Methods and apparatus for communicating transmission backlog information

ABSTRACT

Methods and apparatus for communicating transmission backlog information are described. Reporting control factors are utilized to expand reporting possibilities for a fixed bit size request report. At least one report control factor is determined as a function of channel quality information, power information, device capability information, and/or quality of service information. A transmission backlog report value is interpreted as a function of a reporting control factor. A wide range of quantization schemes for reporting transmission backlog information are facilitated corresponding to a small bit size report. A communications device can adaptively select a quantization request level closely matched to its current needs such as to provide an accurate representation of its current traffic channel resource needs. A communications device may request a number of frames in a request report and the same report may be indirectly requesting a number of communications segments needed to clear its transmission backlog.

RELATED APPLICATIONS

The present application for Patent is a Divisional of patent applicationSer. No. 11/487,054, filed on Jul. 14, 2006, titled “METHODS ANDAPPARATUS FOR COMMUNICATING TRANSMISSION BACKLOG INFORMATION”, pending,which is a Continuation-in-Part of patent application Ser. No.11/333,792, filed on Jan. 17, 2006, titled “METHODS AND APPARATUS OFIMPLEMENTING AND/OR USING A DEDICATED CONTROL CHANNEL”, pending, whichclaims priority to Provisional Application No. 60/752,973, filed on Dec.22, 2005, titled “COMMUNICATIONS METHODS AND APPARATUS”, and assigned tothe assignee hereof and each of which is hereby expressly incorporatedby reference

FIELD OF THE INVENTION

The present invention relates to wireless communications methods andapparatus and, more particularly, to methods and apparatus related tocommunicating transmission backlog information.

BACKGROUND

Wireless terminals that support transmission of uplink traffic, e.g.,user data, from the wireless terminal to a base station normally useuplink air link resources to both communicate control information anduser data. In multiple access wireless communications systems,typically, multiple wireless terminals using a common base stationattachment point are competing for valuable uplink air link resources,e.g., uplink traffic channel air link resources. One approach topartitioning uplink traffic channel resources is for the wirelessterminals to send resource requests to their current base stationattachment point, and for the base station to consider the competingrequests. The base station may then allocate resources, e.g., uplinktraffic channel segments, in accordance with various scheduling rules.

Individual wireless terminals may have different needs for uplinktraffic channel resources at different times, e.g., depending on avariety of factors such as the type(s) of user data to be communicated,latency requirements, predetermined data groupings, and/or prioritylevels. Different types of user data with different transmissionrequirements may be, for example, voice data, image data, Web browserinformation, data files, etc.

Different resource needs may also be due to the fact that an individualwireless terminal may experience different channel quality conditionsand/or have different amounts of power available for transmission atdifferent points in time. Factors such as channel quality and poweravailability can influence acceptable data transmission rates.

A single fixed interpretation uplink traffic channel request reportformat used for a particular type of uplink request report, understoodby the base station and the wireless terminals, and used uniformly inthe system, although simple to implement, is not well suited toefficiently communicate a wide range of uplink traffic channel requestinformation.

Based on the above discussion, it should be appreciated that there is aneed for methods and apparatus for reporting information in an efficientmanner. It would be desirable if at least some efficient reportingmethods could be devised. It would also be desirable if at least somemethods could be used to implement an uplink traffic channel resourcerequest structure which is accommodating to a wide range of wirelessterminal operating conditions, types of wireless terminals and/or blendof applications. It should also be appreciated that for some systemsthere is a need for at least some methods and apparatus which canefficiently communicate the varying needs of individual wirelessterminals for uplink traffic channel resources. Methods and apparatuswhich achieve reporting diversity while accommodating small informationreport size would be beneficial. It would be beneficial if at least somemethods and apparatus facilitate a wide range of quantization schemessuch that a particular quantization scheme well suited to a wirelessterminal at a particular time can be selected and used by the wirelessterminal to communicate backlog information. It would also be beneficialif at least some of the methods and apparatus for efficient reportingwere to make use of available information already being communicatedbetween the wireless terminal and base station such as qualityinformation, thus expanding reporting options while retaining a smallreport bit size.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a drawing of an exemplary communication system implemented inaccordance with various embodiments.

FIG. 2 illustrates an exemplary base station, implemented in accordancewith various embodiments.

FIG. 3 illustrates an exemplary wireless terminal, e.g., mobile node,implemented in accordance with various embodiments.

FIG. 4 is a drawing of exemplary uplink dedicated control channel (DCCH)segments in an exemplary uplink timing and frequency structure in anexemplary orthogonal frequency division multiplexing (OFDM) multipleaccess wireless communications system.

FIG. 5 includes a drawing of an exemplary dedicated control channel inan exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system at a time when each set of DCCH segmentscorresponding to a logical DCCH channel tone is in the full-tone format.

FIG. 6 includes a drawing of an exemplary dedicated control channel inan exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system at a time when each set of DCCH segmentscorresponding to a logical DCCH channel tone is in the split-toneformat.

FIG. 7 includes a drawing of an exemplary dedicated control channel inan exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system at a time when some of the sets of DCCHsegments corresponding to a logical DCCH channel tone are in thefull-tone format and some of the sets of DCCH segments corresponding toa logical DCCH channel tone are in the split-tone format.

FIG. 8 is a drawing illustrating the use of format and mode in anexemplary uplink DCCH in accordance with various embodiments, the modedefining the interpretation of the information bits in the DCCHsegments.

FIG. 9 illustrates several examples corresponding to FIG. 8 illustratingdifferent modes of operation.

FIG. 10 is a drawing illustrating an exemplary default mode of the fulltone format in a beaconslot for a given DCCH tone.

FIG. 11 illustrates an exemplary definition of the default mode in thefull-tone format of the uplink DCCH segments in the first uplinksuperslot after the WT migrates to the ON state.

FIG. 12 is an exemplary summary list of dedicated control reports (DCRs)in the full-tone format for the default mode.

FIG. 13 is a table of an exemplary format for an exemplary 5 bitdownlink SNR report (DLSNR5) in non-DL macrodiversity mode.

FIG. 14 is a table of an exemplary format of 5 bit downlink SNR report(DLSNR5) in DL macrodiversity mode.

FIG. 15 is a table of an exemplary format of an exemplary 3 bit downlinkdelta SNR report (DLDSNR3).

FIG. 16 is a table of an exemplary format for an exemplary 1 bit uplinkrequest (ULRQST1) report.

FIG. 17 is an exemplary table used to calculate exemplary controlparameters y and z, the control parameters y and z being used indetermining uplink multi-bit request reports conveying transmissionrequest group queue information.

FIG. 18 is a table identifying bit format and interpretations associatedwith each of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary first request dictionary (RD referencenumber=0).

FIG. 19 is a table identifying bit format and interpretations associatedwith each of 8 bit patterns for a three bit uplink request, ULRQST3,corresponding to an exemplary first request dictionary (RD referencenumber=0).

FIG. 20 is a table identifying bit format and interpretations associatedwith each of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary second request dictionary (RD referencenumber=1).

FIG. 21 is a table identifying bit format and interpretations associatedwith each of 8 bit patterns for a three bit uplink request, ULRQST3,corresponding to an exemplary second request dictionary (RD referencenumber=1).

FIG. 22 is a table identifying bit format and interpretations associatedwith each of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary third request dictionary (RD referencenumber=2).

FIG. 23 is a table identifying bit format and interpretations associatedwith each of 8 bit patterns for a three bit uplink request, ULRQST3,corresponding to an exemplary third request dictionary (RD referencenumber=2).

FIG. 24 is a table identifying bit format and interpretations associatedwith each of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary fourth request dictionary (RD referencenumber=3).

FIG. 25 is a table identifying bit format and interpretations associatedwith each of 8 bit patterns for a three bit uplink request, ULRQST3,corresponding to an exemplary fourth request dictionary (RD referencenumber=3).

FIG. 26 is a table identifying bit format and interpretations associatedwith each of 32 bit patterns for an exemplary 5 bit uplink transmitterpower backoff report (ULTxBKF5), in accordance with various embodiments.

FIG. 27 includes an exemplary power scaling factor table relating toneblock power tier number to power scaling factor, implemented inaccordance with various embodiments.

FIG. 28 is an exemplary uplink loading factor table used incommunicating base station sector loading information, implemented inaccordance with various embodiments.

FIG. 29 is a table illustrating an exemplary format for a 4 bit downlinkbeacon ratio report (DLBNR4), in accordance with various embodiments.

FIG. 30 is a drawing of an exemplary table describing the format of anexemplary 4 bit downlink self-noise saturation level of SNR report(DLSSNR4), in accordance with various embodiments.

FIG. 31 is a drawing of a table illustrating an example of mappingbetween indicator report information bits and the type of report carriedby the corresponding flexible report.

FIG. 32 is a drawing illustrating an exemplary default mode of the splittone format in a beaconslot for a given DCCH tone for an exemplarywireless terminal.

FIG. 33 illustrates an exemplary definition of the default mode in thesplit-tone format of the uplink DCCH segments in the first uplinksuperslot after the WT migrates to the ON state.

FIG. 34 provides an exemplary summary list of dedicated control reports(DCRs) in the split-tone format for the default mode.

FIG. 35 is a table identifying bit format and interpretations associatedwith each of 16 bit patterns for an exemplary 4 bit uplink transmissionbackoff report (ULTxBKF4), in accordance with various embodiments.

FIG. 36 is an example of mapping between indicator report informationbits and the type of report carried by the corresponding flexiblereport.

FIG. 37 is an exemplary specification of uplink dedicated controlchannel segment modulation coding in full-tone format.

FIG. 38 is a drawing of a table illustrating an exemplary specificationof uplink dedicated control channel segment modulation coding insplit-tone format.

FIG. 39 is a drawing of a table illustrating exemplary wireless terminaluplink traffic channel frame request group queue count information.

FIG. 40 includes drawings illustrating an exemplary set of four requestgroup queues being maintained by a wireless terminal and drawingsillustrating exemplary mappings of uplink data stream traffic flows torequest queues for two exemplary wireless terminals, in accordance withan exemplary embodiment.

FIG. 41 illustrates an exemplary request group queue structure, multiplerequest dictionaries, a plurality of types of uplink traffic channelrequest reports, and grouping of sets of queues in accordance withexemplary formats used for each of the types of reports.

FIG. 42, comprising the combination of FIG. 42A, FIG. 42B, FIG. 42C,FIG. 42D, and FIG. 42E is a flowchart of an exemplary method ofoperating a wireless terminal in accordance with various embodiments.

FIG. 43 is a flowchart of an exemplary method of operating a wirelessterminal in accordance with various embodiments.

FIG. 44 is a flowchart of an exemplary method of operating a wirelessterminal to report control information in accordance with variousembodiments.

FIGS. 45 and 46 are used to illustrate the use of an initial controlinformation report set in an exemplary embodiment.

FIG. 47 is a flowchart of an exemplary method of operating acommunications device in accordance with various embodiments; thecommunications device including information indicating a predeterminedreport sequence for use in controlling the transmission of a pluralityof different control information reports on a recurring basis.

FIG. 48 illustrates two exemplary different formats of initial controlchannel information report sets, the different format report setsincluding at least one segment conveying different sets of reports, inaccordance with various embodiments.

FIG. 49 illustrates a plurality of different initial control informationreport sets in accordance with various embodiments, the differentinitial control information report sets having different numbers ofsegments.

FIG. 50 is a flowchart of an exemplary method of operating a wirelessterminal in accordance with various embodiments.

FIG. 51 is a drawing illustrating exemplary full-tone DCCH mode segmentsand exemplary split-tone DCCH mode segments allocated to exemplarywireless terminals, in accordance with various embodiments.

FIG. 52 is a flowchart of a drawing of an exemplary method of operatinga base station in accordance with various embodiments.

FIG. 53 is a drawing illustrating exemplary full-tone DCCH mode segmentsand exemplary split-tone DCCH mode segments allocated to exemplarywireless terminals, in accordance with various embodiments.

FIG. 54 is a drawing of a flowchart of an exemplary method of operatinga wireless terminal in accordance with various embodiments.

FIG. 55 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 56 is a drawing of an exemplary base station, e.g., access node,implemented in accordance with various embodiments.

FIG. 57 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 58 is a drawing of an exemplary base station, e.g., access node,implemented in accordance with various embodiments.

FIG. 59 comprising the combination of FIG. 59A, FIG. 59B and FIG. 59C isa flowchart of an exemplary method of operating a wireless terminal inaccordance with various embodiments.

FIG. 60 is a flowchart of an exemplary method of operating a wirelessterminal to provide transmission power information to a base station inaccordance with various embodiments.

FIG. 61 is a table of an exemplary format for an exemplary 1 bit uplinkrequest (ULRQST1) report.

FIG. 62 is an exemplary table used to calculate exemplary controlparameters y and z, the control parameters y and z being used indetermining uplink multi-bit request reports conveying transmissionrequest group queue information.

FIG. 63 and FIG. 64 define an exemplary request dictionary with the RDreference number equal to 0.

FIG. 65 and FIG. 66 includes tables which define an exemplary requestdictionary with the RD reference number equal to 1.

FIG. 67 and FIG. 68 include tables which define an exemplary requestdictionary with the RD reference number equal to 2.

FIG. 69 and FIG. 70 include tables which define an exemplary requestdictionary with the RD reference number equal to 3.

FIG. 71 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 72 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 73 illustrates exemplary mapping for an exemplary wireless terminalof uplink data stream traffic flows to its request group queues atdifferent times in accordance with various embodiments.

FIG. 74 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 75 is a drawing used to explain features of an exemplary embodimentusing a wireless terminal transmission power report.

FIG. 76 is a flowchart of an exemplary method of operating a wirelessterminal, e.g., mobile node, to report transmission backlog information.

FIG. 77 comprising the combination of FIG. 77A, FIG. 77B and FIG. 77C isa drawing of a flowchart of an exemplary method of operating a wirelessterminal, e.g., mobile node, to report transmission backlog information.

FIG. 78 is a drawing of an exemplary wireless terminal, e.g., mobilenode, implemented in accordance with various embodiments.

FIG. 79 comprising the combination of FIG. 79A and FIG. 79B is aflowchart of an exemplary method of operating a base station inaccordance with various embodiments.

FIG. 80 comprising the combination of FIG. 80A, FIG. 80B and FIG. 80C isa flowchart of an exemplary method of operating a base station inaccordance with various embodiments.

FIG. 81 is a drawing of an exemplary base station implemented inaccordance with various embodiments.

SUMMARY

Methods and apparatus for communicating transmission backlog informationefficiently are described. Reporting control factors are utilized toexpand reporting possibilities for a fixed bit size request report.

In some but not necessarily all embodiments, a reporting control factoris determined as a function of at least one of: channel qualityinformation, power information, device capability information, qualityof service information, and a communicated parameter. In someimplementations at least one transmission backlog report value isinterpreted as a function of a reporting control factor. Accordingly,the same report value may be interpreted differently depending on thereporting control factor used to interpret the report value. In someembodiments, a wide range of quantization schemes for reportingtransmission backlog information are facilitated corresponding to asmall bit size report. The small bit size report may be, e.g., a reportless than 5 bits in size such as a 4 bit uplink traffic request report.While embodiments with small bit size reports are possible and are oftenpreferable, other larger size reports may be implemented depending onthe embodiment.

In some such embodiments, a communications device, e.g., a wirelessterminal such as a mobile node, can adaptively select a quantizationrequest level closely matched to its current needs such as to provide anaccurate representation of its current traffic channel resource needs. Acommunications device, e.g., a wireless terminal, in some embodiments,may request a number of frames in a request report and the same reportmay be indirectly requesting a number of communications segments neededto clear its transmission backlog, e.g., user data waiting to betransmitted.

In some but not necessarily all embodiments, a communications devicereceiving a request report, e.g., a base station, determines the controlfactor corresponding to a request report and performs an interpretationof a received report value as a function of the determined controlparameter value. Various information, e.g., beacon ratio reportinformation and/or wireless terminal power availability information,already available to both the wireless terminal and base station forother purposes, may be utilized to generate one or more reportingcontrol factors.

An exemplary method of operating a wireless terminal to reporttransmission backlog information includes: (i) generating at least onereporting control factor as a function of at least one of: channelquality information, wireless terminal available transmission powerinformation, wireless terminal device capability information and qualityof service information; and (ii) mapping a number of frames to becommunicated to a report value as a function of said generated at leastone reporting control factor. An exemplary wireless terminal, inaccordance with some embodiments, includes: a control factor generationmodule for generating a control factor as a function of at least one of:channel quality information, wireless terminal available transmissionpower information, wireless terminal device capability information andquality of service information; and a mapping module for mapping anumber of frames to be communicated to a report value as a function ofsaid generated at least one reporting control factor.

An exemplary method of operating a base station in some embodimentsincludes: receiving a transmission backlog report communicating a reportvalue; determining a reporting control factor corresponding to saidreceived backlog report, said reporting control factor being a functionof at least one of: channel quality information, wireless terminalavailable transmission power information, wireless terminal devicecapability information and quality of service information; andinterpreting the received report value as a function of the determinedreporting control factor. An exemplary base station, in some exemplaryembodiments includes: a receiver module for receiving a transmissionbacklog report from a wireless terminal, the transmission backlog reportcommunicating a report value; a reporting control factor determinationmodule for determining a value of a reporting control factor, saidreporting control factor being a function of at least one of: channelquality information, wireless terminal available transmission powerinformation, wireless terminal device capability information and qualityof service information; and a report interpretation module forinterpreting said received report value as a function of a determinedreporting control factor.

While various embodiments have been discussed in the summary above, itshould be appreciated that not necessarily all embodiments include thesame features and some of the features described above are not necessarybut can be desirable in some embodiments. Numerous additional features,embodiments and benefits of the various embodiments are discussed in thedetailed description which follows.

DETAILED DESCRIPTION

FIG. 1 shows an exemplary communication system 100 implemented inaccordance with various embodiments. Exemplary communications system 100includes multiple cells: cell 1 102, cell M 104. Exemplary system 100is, e.g., an exemplary orthogonal frequency division multiplexing (OFDM)spread spectrum wireless communications system such as a multiple accessOFDM system. Each cell 102, 104 of exemplary system 100 includes threesectors. Cells which have not be subdivided into multiple sectors (N=1),cells with two sectors (N=2) and cells with more than 3 sectors (N>3)are also possible in accordance with various embodiments. Each sectorsupports one or more carriers and/or downlink tones blocks. In someembodiments, each downlink tone block has a corresponding uplink toneblock. In some embodiments at least some of the sectors support threedownlink tones blocks. Cell 102 includes a first sector, sector 1 110, asecond sector, sector 2 112, and a third sector, sector 3 114.Similarly, cell M 104 includes a first sector, sector 1 122, a secondsector, sector 2 124, and a third sector, sector 3 126. Cell 1 102includes a base station (BS), base station 1 106, and a plurality ofwireless terminals (WTs) in each sector 110, 112, 114. Sector 1 110includes WT(1) 136 and WT(N) 138 coupled to BS 106 via wireless links140, 142, respectively; sector 2 112 includes WT(1′) 144 and WT(N′) 146coupled to BS 106 via wireless links 148, 150, respectively; sector 3114 includes WT(1″) 152 and WT(N″) 154 coupled to BS 106 via wirelesslinks 156, 158, respectively. Similarly, cell M 104 includes basestation M 108, and a plurality of wireless terminals (WTs) in eachsector 122, 124, 126. Sector 1 122 includes WT(1″″) 168 and WT(N″″) 170coupled to BS M 108 via wireless links 180, 182, respectively; sector 2124 includes WT(1′″″) 172 and WT(N′″″) 174 coupled to BS M 108 viawireless links 184, 186, respectively; sector 3 126 includes WT(1″″″)176 and WT(N″″″) 178 coupled to BS M 108 via wireless links 188, 190,respectively.

System 100 also includes a network node 160 which is coupled to BS1 106and BS M 108 via network links 162, 164, respectively. Network node 160is also coupled to other network nodes, e.g., other base stations, AAAserver nodes, intermediate nodes, routers, etc. and the Internet vianetwork link 166. Network links 162, 164, 166 may be, e.g., fiber opticcables. Each wireless, e.g. WT 1 136, includes a transmitter as well asa receiver. At least some of the wireless terminals, e.g., WT(1) 136,are mobile nodes which may move through system 100 and may communicatevia wireless links with the base station in the cell in which the WT iscurrently located, e.g., using a base station sector attachment point.The wireless terminals, (WTs), e.g. WT(1) 136, may communicate with peernodes, e.g., other WTs in system 100 or outside system 100 via a basestation, e.g. BS 106, and/or network node 160. WTs, e.g., WT(1) 136 maybe mobile communications devices such as cell phones, personal dataassistants with wireless modems, laptop computers with wireless modems,data terminals with wireless modems, etc.

FIG. 2 illustrates an exemplary base station 12, implemented inaccordance with various embodiments. Exemplary base station 12 may beany of the exemplary base stations of FIG. 1. The base station 12includes antennas 203, 205 and receiver transmitter modules 202, 204.The receiver module 202 includes a decoder 233 while the transmittermodule 204 includes an encoder 235. The modules 202, 204 are coupled bya bus 230 to an I/O interface 208, processor (e.g., CPU) 206 and memory210. The I/O interface 208 couples the base station 12 to other networknodes and/or the Internet. The memory 210 includes routines, which whenexecuted by the processor 206, causes the base station 12 to operate.Memory 210 includes communications routines 223 used for controlling thebase station 12 to perform various communications operations andimplement various communications protocols. The memory 210 also includesa base station control routine 225 used to control the base station 12to implement the steps of methods. The base station control routine 225includes a scheduling module 226 used to control transmission schedulingand/or communication resource allocation. Thus, module 226 may serve asa scheduler. Base station control routine 225 also includes dedicatedcontrol channel modules 227 which implement methods, e.g., processingreceived DCCH reports, performing control related to DCCH mode,allocating DCCH segments, etc. Memory 210 also includes information usedby communications routines 223, and control routine 225. Thedata/information 212 includes a set of data/information for a pluralityof wireless terminal (WT 1 data/info 213, WT N data/info 213′. WT 1data/information 213 includes mode information 231, DCCH reportinformation 233, resource information 235 and sessions information 237.Data/information 212 also includes system data/information 229.

FIG. 3 illustrates an exemplary wireless terminal 14, e.g., mobile nodeimplemented in accordance with various embodiments. Exemplary wirelessterminal 14 may be any of the exemplary wireless terminals of FIG. 1.The wireless terminal 14, e.g., mobile node may be used as a mobileterminal (MT). The wireless terminal 14 includes receiver andtransmitter antennas 303, 305 which are coupled to receiver andtransmitter modules 302, 304 respectively. The receiver module 302includes a decoder 333 while the transmitter module 304 includes anencoder 335. The receiver/transmitter modules 302, 304 are coupled by abus 305 to a memory 310. Processor 306, under control of one or moreroutines stored in memory 310 causes the wireless terminal 14 tooperate. In order to control wireless terminal operation memory 310includes communications routine 323 and wireless terminal controlroutine 325. Communications routine 323 is used for controlling thewireless terminal 14 to perform various communications operations andimplement various communications protocols. The wireless terminalcontrol routine 325 is responsible for insuring that the wirelessterminal operates in accordance with the methods and performs the stepsin regard to wireless terminal operations. Wireless terminal controlroutine 325 includes DCCH modules 327, which implement methods, e.g.,control the performing of measurements used in DCCH reports, generateDCCH reports, control transmission of DCCH reports, control DCCH mode,etc. The memory 310 also includes user/device/session/resourceinformation 312 which may be accessed and used to implement the methodsand/or data structures. Information 312 includes DCCH report information330 and mode information 332. Memory 310 also includes systemdata/information 329, e.g., including uplink and downlink channelstructure information.

FIG. 4 is a drawing 400 of exemplary uplink dedicated control channel(DCCH) segments in an exemplary uplink timing and frequency structure inan exemplary orthogonal frequency division multiplexing (OFDM) multipleaccess wireless communications system. The uplink dedicated controlchannel is used to send Dedicated Control Reports (DCR) from wirelessterminals to base stations. Vertical axis 402 plots logical uplink toneindex while horizontal axis 404 plots the uplink index of the halfslotwithin a beaconslot. In this example, an uplink tone block includes 113logical uplink tones indexed (0, . . . , 112); there are sevensuccessive OFDM symbol transmission time periods within a halfslot, 2additional OFDM symbol time periods followed by 16 successive half-slotswithin a superslot, and 8 successive superslots within a beacon slot.The first 9 OFDM symbol transmission time periods within a superslot arean access interval, and the dedicated control channel does not use theair link resources of the access interval.

The exemplary dedicated control channel is subdivided into 31 logicaltones (uplink tone index 81 406, uplink tone index 82 408, . . . ,uplink tone index 111 410). Each logical uplink tone (81, . . . , 111)in the logical uplink frequency structure corresponds to a logical toneindexed with respect to the DCCH channel (0, . . . , 30).

For each tone in the dedicated control channel there are 40 segments inthe beaconslot corresponding to forty columns (412, 414, 416, 418, 420,422, . . . , 424). The segment structure repeats on a beaconslot basis.For a given tone in the dedicated control channel there are 40 segmentscorresponding to a beaconslot 428; each of the eight superslots of thebeaconslot includes 5 successive segments for the given tone. Forexample, for first superslot 426 of beaconslot 428, corresponding totone 0 of the DCCH, there are five indexed segments (segment [0][0],segment [0][1], segment [0][2], segment [0][3], segment [0][4]).Similarly, for first superslot 426 of beaconslot 428, corresponding totone 1 of the DCCH, there are five indexed segments (segment [1][0],segment [1][1], segment [1][2], segment [1][3], segment [1][4]).Similarly, for first superslot 426 of beaconslot 428, corresponding totone 30 of the DCCH, there are five indexed segments (segment [30][0],segment [30][1], segment [30][2], segment [30][3], segment [30][4]).

In this example each segment, e.g., segment [0][0], comprises one tonefor 3 successive half-slots, e.g., representing an allocated uplink airlink resource of 21 OFDM tone-symbols. In some embodiments, logicaluplink tones are hopped to physical tones in accordance with an uplinktone hopping sequence such that the physical tone associated with alogical tone may be different for successive half-slots, but remainsconstant during a given half-slot.

In some embodiments, a set of uplink dedicated control channel segmentscorresponding to a given tone can use one of a plurality of differentformats. For example, in an exemplary embodiment, for a given tone for abeaconslot, the set of DCCH segments can use one of two formats: splittone format and full-tone format. In the full tone format, the set ofuplink DCCH segments corresponding to a tone are used by a singlewireless terminal. In the split tone format, the set of uplink DCCHsegment corresponding to the tone are shared by up to three wirelessterminals in a time division multiplexing manner. The base stationand/or the wireless terminal can, in some embodiments, change the formatfor a given DCCH tone, using predetermined protocols. The format of theuplink DCCH segments corresponding to a different DCCH tone can, in someembodiments, be independently set and may be different.

In some embodiments, in either format, the wireless terminal shallsupport a default mode of the uplink dedicated control channel segments.In some embodiments, the wireless terminal supports the default mode ofthe uplink dedicated control channel segments and one or more additionalmodes of the uplink dedicated control channel segments. Such a modedefines the interpretation of the information bits in the uplinkdedicated control channel segments. The base station and/or the WT can,in some embodiments, change the mode, e.g., using an upper layerconfiguration protocol. In various embodiments, the uplink DCCH segmentscorresponding to a different tone or those corresponding to the sametone but used by different WTs can be independently set and may bedifferent.

FIG. 5 includes a drawing 500 of an exemplary dedicated control channelin an exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system. Drawing 500 may represent the DCCH 400of FIG. 4, at a time when each set of DCCH segments corresponding to atone is in the full-tone format. Vertical axis 502 plots logical toneindex of the DCCH while horizontal axis 504 plots the uplink index ofthe halfslot within a beaconslot. The exemplary dedicated controlchannel is subdivided into 31 logical tones (tone index 0 506, toneindex 1 508, . . . , tone index 30 510). For each tone in the dedicatedcontrol channel there are 40 segments in the beaconslot corresponding toforty columns (512, 514, 516, 518, 520, 522, . . . , 524). Each logicaltone of the dedicated control channel may be assigned by the basestation to a different wireless terminal using the base station as itscurrent point of attachment. For example, logical (tone 0 506, tone 1508, . . . , tone 30 510) may be currently assigned to (WT A 530, WT B532, . . . , WT N′ 534), respectively.

FIG. 6 includes a drawing 600 of an exemplary dedicated control channelin an exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system. Drawing 600 may represent the DCCH 400of FIG. 4, at a time when each set of DCCH segments corresponding to atone is in the split-tone format. Vertical axis 602 plots logical toneindex of the DCCH while horizontal axis 604 plots the uplink index ofthe halfslot within a beaconslot. The exemplary dedicated controlchannel is subdivided into 31 logical tones (tone index 0 606, toneindex 1 608, . . . , tone index 30 610). For each tone in the dedicatedcontrol channel there are 40 segments in the beaconslot corresponding toforty columns (612, 614, 616, 618, 620, 622, . . . , 624). Each logicaltone of the dedicated control channel may be assigned by the basestation to up to 3 different wireless terminals using the base stationas their current point of attachment. For a given tone, the segmentsalternate between the three wireless terminals, with 13 segments beingallocated for each of the three wireless terminals, and the 40^(th)segment is reserved. This exemplary division of air link resources ofthe DCCH channel represents a total of 93 different wireless terminalsbeing allocated DCCH channel resources for the exemplary beaconslot. Forexample, logical tone 0 606 may be currently assigned to and shared byWT A 630, WT B 632, and WT C 634; logical tone 1 608 may be currentlyassigned to and shared by WT D 636, WT E 638, and WT F 640; logical tone30 610 may be currently assigned to WT M′″ 642, WT N′″ 644, and WT O′″646. For the beaconslot, each of the exemplary WTs (630, 632, 634, 636,638, 640, 642, 644, 646) is allocated 13 DCCH segments.

FIG. 7 includes a drawing 700 of an exemplary dedicated control channelin an exemplary uplink timing and frequency structure in an exemplaryorthogonal frequency division multiplexing (OFDM) multiple accesswireless communications system. Drawing 700 may represent the DCCH 400of FIG. 4, at a time when some of the sets of DCCH segmentscorresponding to a tone are in the full-tone format and some of the setsof DCCH segments corresponding to a tone are in the split-tone format.Vertical axis 702 plots logical tone index of the DCCH while horizontalaxis 704 plots the uplink index of the halfslot within a beaconslot. Theexemplary dedicated control channel is subdivided into 31 logical tones(tone index 0 706, tone index 1 708, tone index 2 709, . . . , toneindex 30 710). For each tone in the dedicated control channel there are40 segments in the beaconslot corresponding to forty columns (712, 714,716, 718, 720, 722, . . . , 724). In this example, the set of segmentscorresponding to logical tone 0 708 is in split-tone format and iscurrently assigned to and shared by WT A 730, WT B 732, and WTC 734,each receiving 13 segments with one segment being reserved. The set ofsegments corresponding to logical tone 1 708 is also in split-toneformat, but is currently assigned to and shared by two WTs, WT D 736, WTE 738, each receiving 13 segments. For tone 1 708, there is a set of 13unassigned segments, and one reserved segment. The set of segmentscorresponding to logical tone 2 709 is also in split-tone format, but iscurrently assigned to one WT, WT F 739, receiving 13 segments. For tone2 709, there are two sets with 13 unassigned segments per set, and onereserved segment. The set of segments corresponding to logical tone 30710 is in full-tone format and is currently assigned to WT P′ 740, withWTP′ 740 receiving the full 40 segments to use.

FIG. 8 is a drawing 800 illustrating the use of format and mode in anexemplary uplink DCCH in accordance with various embodiments, the modedefining the interpretation of the information bits in the DCCHsegments. Row 802, corresponding to one tone of the DCCH, illustrates 15successive segments of the DCCH, in which the split tone-format is usedand thus the tone is shared by three wireless terminals, and the modeused by any one of the three WTs can be different. Meanwhile, row 804illustrates 15 successive DCCH segments using the full tone format andis used by a single wireless terminal. Legend 805 indicates that:segments with vertical line shading 806 are used by a 1^(st) WT user,segments with diagonal line shading 808 are used by a 2^(nd) WT user,segments with horizontal line shading 810 are used by a 3^(rd) WT user,and segments with crosshatch shading 812 are used by a 4^(th) WT user.

FIG. 9 illustrates several examples corresponding to drawing 800illustrating different modes of operation. In the example of drawing900, 1^(st), 2^(nd) and 3^(rd) WTs are sharing a DCCH tone in the splittone format while the 4^(th) WT is using a tone in the full tone format.Each of the WTs corresponding to the example of drawing 900 are usingthe default mode of uplink dedicated control channel segments, followinga default mode interpretation of the information bits in the DCCHsegments. The default mode for split tone format (D_(S)) is differentthan the default mode for full tone format (D_(F)).

In the example of drawing 920, 1^(st), 2^(nd) and 3^(rd) WTs are sharinga DCCH tone in the split tone format while the 4^(th) WT is using a tonein the full tone format. Each of the (1^(st), 2^(nd), and 3^(rd)) WTscorresponding to the example of drawing 920 are using different modes ofuplink dedicated control channel segments, each following differentinterpretations of the information bits in the DCCH segments. The 1^(st)WT is using mode 2 for split-tone format, the 2^(nd) wireless terminalis using the default mode for split-tone format, and the 3rd WT is usingmode 1 for split-tone format. In addition the 4^(th) WT is using thedefault mode for full-tone format.

In the example of drawing 940, 1^(st), 2^(nd) and 3^(rd) WTs are sharinga DCCH tone in the split tone format while the 4^(th) WT is using a tonein the full tone format. Each of the (1^(st), 2^(nd), 3^(rd), and4^(th)) WTs corresponding to the example of drawing 940 are usingdifferent modes of uplink dedicated control channel segments, eachfollowing different interpretations of the information bits in the DCCHsegments. The 1^(st) WT is using mode 2 for split-tone format, the2^(nd) wireless terminal is using the default mode for split-toneformat, the 3rd WT is using mode 1 for split tone format, and the 4^(th)WT is using mode 3 for full-tone format.

FIG. 10 is a drawing 1099 illustrating an exemplary default mode of thefull tone format in a beaconslot for a given DCCH tone. In FIG. 10, eachblock (1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010,1011, 1012, 1013, 1014, 1015, 1016, 1017, 1018, 1019, 1020, 1021, 1022,1023, 1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 1033, 1034,1035, 1036, 1037, 1038, 1039) represents one segment whose index s2 (0,. . . , 39) is shown above the block in rectangular region 1040. Eachblock, e.g., block 1000 representing segment 0, conveys 6 informationbits; each block comprises 6 rows corresponding to the 6 bits in thesegment, where the bits are listed from the most significant bit to theleast significant bit downwards from the top row to the bottom row asshown in rectangular region 1043.

For the exemplary embodiment, the framing format shown in FIG. 10 isused repeatedly in every beaconslot, when the default mode of full-toneformat is used, with the following exception. In the first uplinksuperslot after the wireless terminal migrates to the ON state in thecurrent connection, the WT shall use the framing format shown in FIG.11. The first uplink superslot is defined: for a scenario when the WTmigrates to the ON state from the ACCESS state, for a scenario when theWT migrates to the ON state from a HOLD state, and for a scenario whenthe WT migrates to the ON state from the ON state of another connection.

FIG. 11 illustrates an exemplary definition of the default mode in thefull-tone format of the uplink DCCH segments in the first uplinksuperslot after the WT migrates to the ON state. Drawing 1199 includesfive successive segments (1100, 1101, 1102, 1103, 1104) corresponding tosegment index numbers, s2=(0, 1, 2, 3, 4), respectively in the superslotas indicated by rectangle 1106 above the segments. Each block, e.g.,block 1100 representing segment 0 of the superslot, conveys 6information bits; each block comprises 6 rows corresponding to the 6bits in the segment, where the bits are listed from the most significantbit to the least significant bit downwards from the top row to thebottom row as shown in rectangular region 1108.

In the exemplary embodiment, in the scenario of migrating from the HOLDto ON state, the WT starts to transmit the uplink DCCH channel from thebeginning of the first UL superslot, and therefore the first uplink DCCHsegment shall transport the information bits in the leftmost informationcolumn of FIG. 11, the information bits of segment 1100. In theexemplary embodiment, in the scenario of migrating from the ACCESSstate, the WT does not necessarily start from the beginning of the firstUL superslot, but does still transmit the uplink DCCH segments accordingto the framing format specified in FIG. 11. For example, if the WTstarts to transmit the UL DCCH segments from the halfslot of thesuperslot with index=4, then the WT skips the leftmost informationcolumn of FIG. 11 (segment 1100) and the first uplink DCCH segmenttransports the second leftmost column (segment 1101). Note that in theexemplary embodiment, superslot indexed halfslots (1-3) correspond toone DCCH segment (1100) and superslot indexed halfslots (4-6) correspondto the next segment (1101). In the exemplary embodiment, for thescenario of switching between the full-tone and split-tone formats, theWT uses the framing format shown in FIG. 10 without the above exceptionof using the format shown in FIG. 11.

Once, the first UL superslot ends, the uplink DCCH channel segmentsswitch to the framing format of FIG. 10. Depending on where the firstuplink superslot ends, the point of switching the framing format may ormay not be the beginning of a beaconslot. Note that in this exampleembodiment, there are five DCCH segments for a given DCCH tone for asuperslot. For example, suppose that the first uplink superslot is ofuplink beaconslot superslot index=2, where beaconslot superslot indexrange is from 0 to 7. Subsequently in the next uplink superslot, whichis of uplink beaconslot superslot index=3, the first uplink DCCH segmentusing the default framing format of FIG. 10 is of index s2=15 (segment1015 of FIG. 10) and transports the information corresponding to segments2=15 (segment 1015 of FIG. 10).

Each uplink DCCH segment is used to transmit a set of Dedicated ControlChannel Reports (DCRs). An exemplary summary list of DCRs in thefull-tone format for the default mode is given in table 1200 FIG. 12.The information of table 1200 is applicable to the partitioned segmentsof FIGS. 10 and 11. Each segment of FIGS. 10 and 11 includes two or morereports as described in table 1200. First column 1202 of table 1200describes abbreviated names used for each exemplary report. The name ofeach report ends with a number which specifies the number of bits of theDCR. Second column 1204 of table 1200 briefly describes each namedreport. Third column 1206 specifies the segment index s2 of FIG. 10, inwhich a DCR is to be transmitted, and corresponds to a mapping betweentable 1200 and FIG. 10.

The exemplary 5 bit absolute report of downlink signal to noise ratio(DLSNR5) shall now be described. The exemplary DLSNR5 uses one of thefollowing two mode formats. When the WT has only one connection, thenon-DL macrodiversity mode format is used. When the WT has multipleconnections, the DL-macrodiversity mode format is used if the WT is inthe DL-macrodiversity mode; otherwise the non-macrodiversity mode formatis used. In some embodiments, whether the WT is in the DL-macrodiversitymode and/or how the WT switches between the DL macrodiversity mode andthe non-DL macrodiversity mode are specified in an upper layer protocol.In the non-DL macro-diversity mode the WT reports the measured receiveddownlink pilot channel segment SNR using the closest representation ofTable 1300 of FIG. 13. FIG. 13 is a table 1300 of an exemplary format ofDLSNR5 in non-DL macrodiversity mode. First column 1302 list 32 possiblebit pattern that may be represented by the 5 bits of the report. Secondcolumn 1304 lists the value of wtDLPICHSNR being communicated to thebase station via the report. In this example, incremental levels from−12 dB to 29 dB can be indicated corresponding to 31 different bitpatterns, while bit pattern 11111 is reserved.

For example, if the calculated wtDLPICHSNR based on measurement is −14dB, the DLSNR5 report is set to bit pattern 00000; if the calculatedwtDLPICHSNR based on measurement is −11.6 dB, the DLSNR5 report is setto bit pattern 00000 because in table 1300 the entry with −12 dB is thecloset to the calculated value of −11.6 dB; if the calculatedwtDLPICHSNR based on measurement is −11.4 dB, the DLSNR5 report is setto bit pattern 00001 because in table 1300 the entry with −11 dB is thecloset to the calculated value of −11.4 dB.

The reported wireless terminal downlink pilot SNR (wtDLPICHSNR) accountsfor the fact that the pilot signal, on which the SNR is measured, istypically transmitted at higher power than the average traffic channelpower. For this reason, the pilot SNR is, in some embodiments, reportedas,wtDLPICHSNR=PilotSNR−Delta,where pilotSNR is the measured SNR on the received downlink pilotchannel signal in dB, and Delta is a difference between the pilottransmission power and an average per tone channel transmission powerlevel, e.g. the average per tone downlink traffic channel transmissionpower. In some embodiments Delta=7.5 dB.

In the DL-macrodiversity mode format the WT uses the DLSNR5 report toinform a base station sector attachment point, whether the currentdownlink connection with the base station sector attachment point is apreferred connection, and to report the calculated wtDLPICHSNR with theclosest DLSNR5 report according to table 1400. FIG. 14 is a table 1400of an exemplary format of DLSNR5 in DL macrodiversity mode. First column1402 list 32 possible bit patterns that may be represented by the 5 bitsof the report. Second column 1404 lists the value of wtDLPICHSNR beingcommunicated to the base station via the report and an indication as towhether or not the connection is preferred. In this example, incrementallevels of SNR from −12 db to 13 dB can be indicated corresponding to 32different bit patterns. Sixteen of the bit patterns correspond to thecase where the connection is not preferred; while the remaining sixteenbit patterns correspond to the case where the connection is preferred.In some exemplary embodiments, the highest SNR value that can beindicated when a link is preferred is greater than the highest SNR valuethat can be indicated when a link is not preferred. In some exemplaryembodiments, the lowest SNR that can be indicated when a link ispreferred is greater than the lowest SNR value that can be indicatedwhen a link is not preferred.

In some embodiments, in the DL-macrodiversity mode, the wirelessterminal indicates one and only one connection to be the preferredconnection at any given time. Furthermore, in some such embodiments, ifthe WT indicates that a connection is preferred in a DLSNR5 report, thenthe WT sends at least NumConsecutive Preferred consecutive DLSNR5reports indicating that the connection is preferred before the WT isallowed to a send a DLSNR5 report indicating that another connectionbecomes the preferred one. The value of the parameter NumConsecutivepreferred depends on the format of the uplink DCCH channel, e.g.,full-tone format vs split-tone format). In some embodiments the WT getsthe parameter NumConsecutivePreferred in an upper level protocol. Insome embodiments, the default value of NumConsecutivePreferred is 10 inthe full-tone format.

An exemplary 3 bit relative (difference) report of downlink SNR(DLDSNR3) shall now be described. The wireless terminal measures thereceived SNR of the downlink pilot channel (PilotSNR), calculates thewtDLPICHSNR value, where wtDLPICHSNR=PilotSNR−Delta, calculates thedifference between the calculated wtDLPICHSNR value and the reportedvalue by the most recent DLSNR5 report, and reports the calculateddifference with the closest DLDSNR3 report according to table 1500 ofFIG. 15. FIG. 15 is a table 1500 of an exemplary format of DLDSNR3.First column 1502 lists 9 possible bit patterns that may represent the 3information bits of the report. Second column 1504 lists the reporteddifference in wtDLPICHSNR being communicated to the base station via thereport ranging from −5 dB to 5 dB.

Various exemplary uplink traffic channel request reports will now bedescribed. In an exemplary embodiment three types of uplink trafficchannel request reports are used: an exemplary single bit uplink trafficchannel request report (ULRQST1), an exemplary three bit uplink trafficchannel request report (ULRQST3), and an exemplary four bit uplinktraffic channel request report (ULRQST4). The WT uses an ULRQST1,ULRQST3, or ULRQST4 to report the status of the MAC frame queues at theWT transmitter. In the exemplary embodiment, the MAC frames areconstructed from the LLC frames, which are constructed from packets ofupper layer protocols. In this exemplary embodiment, any packet belongsto one of four request groups (RG0, RG1, RG2, or RG3). In some exemplaryembodiments, the mapping of packets to request groups is done throughhigher layer protocols. In some exemplary embodiments, there is adefault mapping of packets to request groups, that may be changed by thebase station and/or WT through higher layer protocols. If the packetbelongs to one request group, then, in this exemplary embodiment, allthe MAC frames of that packet also belong to that same request group.The WT reports the number of MAC frames in the 4 request groups that theWT may intend to transmit. In the ARQ protocol, those MAC frames aremarked as “new” or “to be retransmitted”. The WT maintains a vector offour elements N[0:3] for k=0:3, N[k] represents the number of MAC framesthat the WT intends to transmit in request group k. The WT should reportthe information about N[0:3] to the base station sector so that the basestation sector can utilize the information in an uplink schedulingalgorithm to determine the assignment of uplink traffic channelsegments.

In an exemplary embodiment, the WT uses the single bit uplink trafficchannel request report (ULRQST1) to report N[0]+N[1] according to table1600 of FIG. 16. Table 1600 is an exemplary format for an ULRQST1report. First column 1602 indicates the two possible bit patterns thatmay be conveyed while second column 1604 indicates the meaning of eachbit pattern. If the bit pattern is 0, that indicates that there are noMAC frames that the WT intends to transmit in either request group 0 orrequest group 1. If the bit pattern is 1, that indicates that the WT hasat least one MAC frame in request group 0 or request group 1 that the WTintends to communicate.

In accordance with a feature used in various embodiments, multiplerequest dictionaries are supported. Such a request dictionary definesthe interpretation of the information bits in uplink traffic channelrequest reports in the uplink dedicated control channel segments. At agiven time, the WT uses one request dictionary. In some embodiments,when the WT just enters the ACTIVE state, the WT uses a default requestdictionary. To change the request dictionary the WT and base stationsector use an upper layer configuration protocol. In some embodiments,when the WT migrates from the ON state to the HOLD state, the WT keepsthe last request dictionary used in the ON state so that when the WTmigrates from the HOLD state to the ON state later, the WT continues touse the same request dictionary until the request dictionary isexplicitly changed; however, if the WT leaves the ACTIVE state, then thememory of the last request dictionary is cleared. In some embodiments,the ACTIVE state includes the ON state and the Hold state, but does notinclude the ACCESS state and sleep state.

In some embodiments, to determine at least some ULRQST3 or ULRQST4reports, the wireless terminal first calculates one or more of thefollowing two control parameters y and z, and uses one of the requestdictionaries, e.g., Request dictionary (RD) reference number 0, RDreference number 1, RD reference number 2, RD reference number 3. Table1700 of FIG. 17 is an exemplary table used to calculate controlparameters y and z. First column 1702 lists a condition; second column1704 lists the corresponding value of output control parameter y; thirdcolumn 1706 lists the corresponding value of output control parameter z.In first column 1702, x (in dBs) represents the value of the most recent5 bit uplink transmit backoff report (ULTXBKF5) and the value b (in dBs)of the most recent 4 bit downlink beacon ratio report (DLBNR4). Giventhe input values of x and b from the most recent reports, the WT checksif the condition from first row 1710 is satisfied. If the test conditionis satisfied, then the WT uses the corresponding y and z values of therow for calculating the ULRQST3 or ULRQST4. However, if the condition isnot satisfied the testing continues with the next row 1712. Testingcontinues proceeding down the table 1700 in order from top to bottom(1710, 1712, 1714, 1716, 1718, 1720, 1722, 1724, 1726, 1728) until thecondition listed in column 1702 for a given row is satisfied. The WTdetermines y and z as those from the first row in table 1700 for whichthe first column is satisfied. For example, if x=17 and b=1, then z=4and y=1.

The WT, in some embodiments, uses an ULRQST3 or ULRQST4 to report theactual N[0:3] of the MAC frames queues according to a requestdictionary. A request dictionary is identified by a request dictionary(RD) reference number.

In some embodiments, at least some request dictionaries are such thatany ULRQST4 or ULRQST3 may not completely include the actual N[0:3]. Areport is in effect a quantized version of the actual N[0:3]. In someembodiments, the WT sends a report to minimize the discrepancy betweenthe reported and actual MAC frame queues first for request group 0 and1, and then for request group 2, and finally for request group 3.However, in some embodiments, the WT has the flexibility of determininga report to benefit the WT most. For example, assume that the WT isusing exemplary request dictionary 1 (See FIGS. 20 and 21), the WT mayuse an ULRQST4 to report N[1]+N[3] and use an ULRQST3 to report N[2] andN[0]. In addition if a report is directly related to a subset of requestgroups according to the request dictionary, it does not automaticallyimply that MAC frame queues of a remaining request group are empty. Forexample, if a report means N[2]=1, then it may not automatically implythat N[0]=0, N[1]=0, or N[3]=0.

FIG. 18 is a table 1800 identifying bit format and interpretationsassociated with each of 16 bit patterns for a four bit uplink request,ULRQST4, corresponding to an exemplary first request dictionary (RDreference number=0). In some embodiments, the request dictionary withreference number=0 is the default request dictionary. First column 1802identifies the bit pattern and bit ordering, most significant bit toleast significant bit. Second column 1804 identifies the interpretationassociated with each bit pattern. An ULRQST4 of table 1800 conveys oneof: (i) no change from the previous 4 bit uplink request, (ii)information about the N[0], and (iii) information about a composite ofN[1]+N[2]+N[3] as a function of either control parameter y or controlparameter z of table 1700 of FIG. 17.

FIG. 19 is a table 1900 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary first request dictionary (RDreference number=0). In some embodiments, the request dictionary withreference number=0 is the default request dictionary. First column 1902identifies the bit pattern and bit ordering, most significant bit toleast significant bit. Second column 1904 identifies the interpretationassociated with each bit pattern. An ULRQST3 of table 1900 conveys: (i)information about the N[0] and (ii) information about a composite ofN[1]+N[2]+N[3] as a function of control parameter y of table 1700 ofFIG. 17.

FIG. 20 is a table 2000 identifying bit format and interpretationsassociated with each of 16 bit patterns for a four bit uplink request,ULRQST4, corresponding to an exemplary second request dictionary (RDreference number=1). First column 2002 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2004 identifies the interpretation associated with each bitpattern. An ULRQST4 of table 2000 conveys one of: (i) no change from theprevious 4 bit uplink request, (ii) information about the N[2], and(iii) information about a composite of N[1]+N[3] as a function of eithercontrol parameter y or control parameter z of table 1700 of FIG. 17.

FIG. 21 is a table 2100 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary second request dictionary (RDreference number=1). First column 2102 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2104 identifies the interpretation associated with each bitpattern. An ULRQST3 of table 2100 conveys: (i) information about N[0]and (ii) information about N[2].

FIG. 22 is a table 2200 identifying bit format and interpretationsassociated with each of 16 bit patterns for a four bit uplink request,ULRQST4, corresponding to an exemplary third request dictionary (RDreference number=2). First column 2202 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2204 identifies the interpretation associated with each bitpattern. An ULRQST4 of table 2200 conveys one of: (i) no change from theprevious 4 bit uplink request, (ii) information about the N[1], and(iii) information about a composite of N[2]+N[3] as a function of eithercontrol parameter y or control parameter z of table 1700 of FIG. 17.

FIG. 23 is a table 2300 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary third request dictionary (RDreference number=2). First column 2302 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2304 identifies the interpretation associated with each bitpattern. An ULRQST3 of table 2300 conveys: (i) information about N[0]and (ii) information about N[1].

FIG. 24 is a table 2400 identifying bit format and interpretationsassociated with each of 16 bit patterns for a four bit uplink request,ULRQST4, corresponding to an exemplary fourth request dictionary (RDreference number=3). First column 2402 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2404 identifies the interpretation associated with each bitpattern. An ULRQST4 of table 2400 conveys one of: (i) no change from theprevious 4 bit uplink request, (ii) information about N[1], (iii)information about N[2], and (iv) information about N[3] as a function ofeither control parameter y or control parameter z of table 1700 of FIG.17.

FIG. 25 is a table 2500 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary fourth request dictionary (RDreference number=3). First column 2502 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 2504 identifies the interpretation associated with each bitpattern. An ULRQST3 of table 2500 conveys: (i) information about N[0]and (ii) information about N[1].

In accordance with various embodiments, the methods facilitate a widerange of reporting possibilities. For example, the use of controlparameters, e.g., based on SNR and backoff reports, allow for a singlebit pattern request corresponding to a given dictionary to take onmultiple interpretations. Consider exemplary request dictionaryreference number 0 for 4 bit uplink requests as shown in table 1800 ofFIG. 18. For a four bit request where each bit pattern corresponds to afixed interpretations and does not rely on control parameters, 16possibilities exists. However, in table 1800 four of the bit patterns(0011, 0100, 0101, and 0110) can each have two different interpretationssince control parameter y can have value 1 or 2. Similarly, in table1800 nine of the bit patterns (0111, 1000, 1001, 1010, 1011, 1100, 1101,1110, and 1111) can each have 10 different interpretations since controlparameter z can have any of the values (1, 2, 3, 4, 5, 6, 7, 8, 9, 10).This use of control parameters expands the range of reporting for the 4bit request report from 16 different possibilities to 111 possibilities.

An exemplary 5 bit wireless terminal transmitter power backoff report(ULTxBKF5) will now be described. A wireless terminal backoff reportreports an amount of remaining power that the WT has to use for uplinktransmissions for non-DCCH segments, e.g., including uplink trafficchannel segment(s) after taking into account the power used to transmitthe DCCH segments. wtULDCCHBackOff=wtPowerMax−wtULDCCHTxPower; wherewtULDCCHTxPower denotes the per-tone transmission power of the uplinkDCCH channel in dBm, and wtPowerMax is the maximum transmission powervalue of the WT, also in dBm. Note that the wtULDCCHTxPower representsthe instantaneous power and is calculated using the wtPowerNominal inthe halfslot immediately preceeding the current uplink DCCH segment. Insome such embodiments, the per tone power of the uplink DCCH channelrelative to wtPowerNominal is 0 dBs. The value of wtPowerMax depends onthe device capability of the WT, upon system specifications and/or uponregulations. In some embodiments, the determination of wtPowerMax isimplementation dependent.

FIG. 26 is a table 2600 identifying bit format and interpretationsassociated with each of 32 bit patterns for an exemplary 5 bit uplinktransmitter power backoff report (ULTxBKF5), in accordance with variousembodiments. First column 2602 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column2604 identifies the reported WT uplink DCCH Backoff report values in dBscorresponding to each bit pattern. In this exemplary embodiment 30distinct levels can be reported ranging from 6.5 dB to 40 dBs; two bitpatterns are left as reserved. A wireless terminal calculateswtULDCCHBackoff, e.g., as indicated above, selects the closet entry intable 2600 and uses that bit pattern for the report.

An exemplary 4 bit downlink beacon ratio report (DLBNR4) will now bedescribed. The beacon ratio report provides information which is afunction of received measured downlink broadcast signals, e.g., beaconsignals and/or pilot signals, from a serving base station sector andfrom one or more other interfering base station sectors. Qualitatively,the beacon ratio report can be used to estimate the relative proximityof the WT to other base station sectors. The beacon ratio report can be,and in some embodiments is, used at the serving BS sector in controllingthe uplink rate of the WT to prevent excessive interference to othersectors. The beacon ratio report, in some embodiments, is based on twofactors: (i) estimated channel gain ratios, denoted G_(i), and (ii)loading factors, denoted b_(i).

The channel gain ratios are defined, in some embodiments, as follows. Inthe tone block of the current connection, the WT, in some embodiments,determines an estimate of the ratio of the uplink channel gain from theWT to any interfering Base station sector i (BSS i) to the channel gainfrom the WT to the serving BSS. This ratio is denoted as G_(i).Typically, the uplink channel gain ratio is not directly measurable atthe WT. However, since the uplink and downlink path gains are typicallysymmetric, the ratio can be estimated by comparing the relative receivedpower of downlink signals from the serving and interfering BSSs. Onepossible choice for the reference downlink signal is the downlink beaconsignal, which is well-suited for this purpose since it can be detectedin very low SNR. In some embodiments, beacon signals have a higher pertone transmission power level than other downlink signals from a basestation sector. Additionally, the characteristics of the beacon signalare such that precise timing synchronization is not necessary to detectand measure the beacon signal. For example, the beacon signal is, insome embodiments, a high power narrowband, e.g., single tone, two OFDMsymbol transmission time period wide signal. Thus at certain locations,a WT is able to detect and measure a beacon signal from a base stationsector, where the detection and/or measurement of other downlinkbroadcast signals, e.g., pilot signals may not be feasible. Using thebeacon signal, the uplink path ratio would be given by G_(i)=PB_(i)/PB₀,where PB_(i) and PB₀ are, respectively, the measured received beaconpower from the interfering and serving base station sectors,respectively.

Since the beacon is typically transmitted rather infrequently, the powermeasurement of the beacon signal may not provide a very accuraterepresentation of average channel gain, especially in a fadingenvironment where the power changes rapidly. For example, in someembodiments one beacon signal, which occupies 2 successive OFDM symboltransmission time periods in duration and which corresponds to adownlink tone block of a base station sector, is transmitted for everybeaconslot of 912 OFDM symbol transmission time periods.

Pilot signals, on the other hand, are often transmitted much morefrequently than beacon signals, e.g., in some embodiments pilot signalsare transmitted during 896 out of the 912 OFDM symbol transmission timeperiods of a beaconslot. If the WT can detect the pilot signal from theBS sector, it can estimate the received beacon signal strength from themeasured received pilot signal instead of using a beacon signalmeasurement. For example, if the WT can measure the received pilotpower, PP_(i,) of the interfering BS sector, then it can estimate thereceived beacon power PB_(i) from estimated PB_(i)=KZ_(i)PP_(i,) where Kis a nominal ratio of the beacon to pilot power of the interferingsector that is the same for each of the BS sectors, and Z_(i) is ascaling factor that is sector dependent.

Similarly, if the pilot signal power from the serving BS is measurableat the WT, then the received beacon power PB₀ can be estimated from therelation, estimated PB₀=KZ₀PP₀, where Z₀ and PP₀ are, respectively, thescaling factor and measured received pilot power from the serving basestation sector.

Observe that if the received pilot signal strength is measurablecorresponding to the serving base station sector, and the receivedbeacon signal strength is measurable corresponding to interfering basestation sector, the beacon ratio can be estimated from:G _(i) =PB _(i)/(PP ₀ KZ ₀)

Observe that if the pilot strengths are measurable in both the servingand interfering sectors, the beacon ratio can be estimated from:G _(i) =PP _(i) KZ _(i)/(PP ₀ KZ ₀)=PP _(i) Z _(i)/(PP ₀ Z ₀).

The scaling factors K, Z, and Z₀ are either system constants, or can beinferred by the WT, from other information from the BS. In someembodiments, some of the scaling factors (K, Z_(i), Z₀) are systemconstants and some of the scaling factors (K, Z_(i), Z₀) are inferred bythe WT, from other information form the BS.

In some multicarrier systems with different power levels on differentcarriers, the scaling factors, Z_(i) and Z₀, are a function of thedownlink tone block. For example, an exemplary BSS has three power tierlevels, and one of the three power tier levels is associated with eachdownlink tone block corresponding to a BSS attachment point. In somesuch embodiments, a different one of the three power tier levels isassociated with each of the different tone blocks of the BSS. Continuingwith the example, for the given BSS, each power tier level is associatedwith a nominal bss power level (e.g., one of bssPowerNominal0,bssPowerNominal1, and bssPowerNominal2) and the pilot channel signal istransmitted at a relative power level with respect to a nominal bsspower level for the tone block, e.g., 7.2 dB above the nominal bss powerlevel being used by the tone block; however, the beacon per tonerelative transmission power level for the BSS is the same irrespectiveof the tone block from which the beacon is transmitted, e.g., 23.8 dBabove the bss power level used by the power tier 0 block(bssPowerNominal0). Consequently, in this example for a given BSS, thebeacon transmit power would be the same in each of the tone blocks,while the pilot transmit power is different, e.g. with the pilottransmit power of different tone blocks corresponding to different powertier levels. One set of scale factors for this example would be,K=23.8−7.2 dB, which is the ratio of the beacon to pilot power for tier0, and Z_(i) is set to the relative nominal power of the tier of theinterfering sector to the power of a tier 0 sector.

In some embodiments, the parameter Z₀ is determined from storedinformation, e.g., Table 2700 of FIG. 27, according to how the toneblock of the current connection is used in the serving BSS as determinedby the bssSectorType of the serving BSS. For example, if the tone blockof the current connection is used as a tier 0 tone block by the servingBSS, the Z₀=1; if the tone block of the current connection is used as atier 1 tone block by the serving BSS, the Z₀=bssPowerBackoff01; if thetone block of the current connection is used as a tier 2 tone block bythe serving BSS, the Z₀=bssPowerBackoff02.

FIG. 27 includes exemplary power scaling factor table 2700, implementedin accordance with various embodiments. First column 2702 lists the useof the tone block as either a tier 0 tone block, tier 1 tone block, ortier 2 tone block. Second column 2704 lists the scaling factorassociated with each tier (0,1,2) tone block, as (1, bssPowerBackoff01,bssPowerBackoff02), respectively. In some embodiments, bssPowerBackoff01is 6 dBs while bssPowerBackoff02 is 12 dB.

In some embodiments, the DCCH DLBNR4 report can be one of a genericbeacon ratio report and a special beacon ratio report. In some suchembodiments, a downlink traffic control channel, e.g., a DL.TCCH.FLASHchannel, sends a special frame in a beaconslot, the special frameincluding a “Request for DLBNR4 report field”. That field can be used bythe serving BSS to control the selection. For example, if the field isset to zero then, the WT reports a generic beacon ratio report;otherwise the WT reports the special beacon ratio report.

A generic beacon ratio report, in accordance with some embodiments,measures the relative interference cost the WT would generate to all theinterfering beacons or the “closest” interfering beacon, if the WT wereto transmit to the serving BSS in the current connection. A specialbeacon ratio report, in accordance with some embodiments, measures therelative interference cost the WT would generate to a specific BSS, ifthe WT were to transmit to the serving BSS in the current connection.The specific BSS is the one indicated using information received in theRequest for DLBNR4 field of the special downlink frame. For example, insome embodiments, the specific BSS is the one whose bssSlope is equal tothe value of the “Request for DLBNR4 report field”, e.g., in unsignedinteger format, and whose bssSectorType is equal tomod(ulUltraslotBeaconslotIndex,3), where ulUltraslotBeaconslotIndex isthe uplink index of the beaconslot within the ultraslot of the currentconnection. In some exemplary embodiments, there are 18 indexedbeaconslots within an ultraslot.

In various embodiments, both the generic and the special beacon ratiosare determined from the calculated channel gain ratios G1, G2, . . . ,as follows. The WT receives an uplink loading factor sent in a downlinkbroadcast system subchannel and determines a variable b₀ from uplinkloading factor table 2800 of FIG. 28. Table 2800 includes a first column2802 listing eight different values that may be used for the uplinkloading factor (0, 1, 2, 3, 4, 5, 6, 7); second column lists thecorresponding values for the b value in dB (0, −1, −2, −3, −4, −6, −9,−infinity), respectively. For other BSSi, the WT attempts to receiveb_(i) from the uplink loading factor sent in the downlink broadcastsystem subchannel of the BSS i in the tone block of the currentconnection. If the WT is unable to receive the UL loading factor bi, theWT sets b_(i)=1.

In some embodiments, in the single carrier operation, the WT calculatesthe following power ratio as the generic beacon ratio report:b₀/(G₁b₁+G₂b₂+ . . . ) when ulUltraslotBeaconslot Index is even orb0/max(G₁b₁, G₂b₂, . . . ) when ulUltraslotBeaconslotIndex is odd, whereulUltraslotBeaconslotIndex is the uplink index of the beaconslot withinthe ultraslot of the current connection and the operation+ represents aregular addition. When required to send a specific beacon ratio report,the WT, in some embodiments, calculates b₀/(G_(k)B_(k)), where index krepresents the specific BSS k. In some embodiments, there are 18 indexedbeaconslots within an ultraslot.

FIG. 29 is a table 2900 illustrating an exemplary format for a 4 bitdownlink beacon ratio report (DLBNR4), in accordance with variousembodiments. First column 2902 lists the 16 various bit patterns thatthe report can convey, while second column 2904 lists the reported powerratio reported corresponding to each bit pattern, e.g., ranging from −3dB to 26 dBs. The wireless terminal reports the generic and specificbeacon ratio reports by selecting and communicating the DLBNR4 tableentry that is closed to the determined report value. Although in thisexemplary embodiment, the generic and specific beacon ratio reports usethe same table for DLBNR4, in some embodiments, different tables may beused.

An exemplary 4 bit saturation level of downlink self-noise SNR report(DLSSNR4) will now be described. In some embodiments, the WT derives thesaturation level of the DL SNR, which is defined to be the DL SNR thatthe WT receiver would measure on a received signal if the BSStransmitted the signal at infinite power, if the base station werecapable of transmitting such a signal and the wireless terminal wascapable of measuring such a signal. The saturation level can be, and insome embodiments is, determined by the self-noise of the WT receiver,which may be caused by factor such as channel estimation errors. Thefollowing is an exemplary method to derive the saturation level of theDL SNR.

In the exemplary method, the WT assumes that if the BSS transmits atpower P, the DL SNR is equal to SNR(P)=GP/(a₀GP+N), where G representthe wireless channel path gain from the BSS to the WT, P is thetransmission power, so that GP is the received signal power, Nrepresents the received interference power, a₀GP represents theself-noise, where a higher value of a₀ denotes a higher value ofself-noise. G is a value between 0 and 1, a₀, P, and N are positivevalues. In this model, by definition, the saturation level of the DL SNRis equal to 1/a₀. In some embodiments, the WT measures the receivedpower of a downlink Null channel (DL.NCH) to determine the interferencepower N, measures the received power (denoted as G*P₀) of the downlinkpilot channel and SNR (denoted by SNR₀) of the downlink pilot channel;the WT then calculates 1/a₀=(1/SNR₀−N/(GP₀))⁻¹.

Once the WT has derived the saturation level of the DL SNR, the WTreports it by using the closest entry to the derived value in a DLself-noise saturation level report table. Table 3000 of FIG. 30 is suchan exemplary table describing the format of DLSSNR4. First column 3002indicates the 16 different possible bit patterns that can be conveyed bythe DLSSNR4 report, and second column 3004 lists saturation levels of DLSNR that are communicated corresponding to each bit pattern ranging from8.75 dB to 29.75 dBs.

In various embodiments, a flexible report is included in the DCCH, suchthat the WT decides which type of report to communicate and, the type ofreport can change from one flexible reporting opportunity to the nextfor a given WT using its allocated dedicated control channel segments.

In an exemplary embodiment, the WT uses a 2 bit type report (TYPE2) toindicate the type of report selected by the WT to be communicated in a 4bit body report (BODY4) of the same DCCH segment including both theTYPE2 and BODY4 reports. Table 3100 of FIG. 31 is an example of mappingbetween TYPE2 report information bits and the type of report carried bythe corresponding BODY4 report. First column 3102 indicates the fourpossible bit patterns for the 2 bit TYPE2 report. Second column 3104indicates the type of report to be carried in the BODY4 report of thesame uplink dedicated control channel segment corresponding to the TYPE2report. Table 3100 indicates that: bit pattern 00 indicates that BODY4report will be an ULRQST4 report, Bit pattern 01 indicates the BODY4report will be a DLSSNR4 report, and bit patterns 10 and 11 arereserved.

In some embodiments, a WT selects the TYPE2 and BODY4 reports byassessing the relative importance of the different types of reports fromamong which the selection may occur, e.g., the reports listed in table3100. In some embodiments, the WT can select the TYPE2 independentlyfrom one segment to another.

FIG. 32 is a drawing 3299 illustrating an exemplary default mode of thesplit tone format in a beaconslot for a given DCCH tone for a first WT.In FIG. 32, each block (3200, 3201, 3202, 3203 3204, 3205, 3206, 3207,3208, 3209, 3210, 3211, 3212, 3213, 3214, 3215, 3216, 3217, 3218, 3219,3220, 3221, 3222, 3223, 3224, 3225, 3226, 3227, 3228, 3229, 3230, 3231,3232, 3323, 3234, 3235, 3236, 3237, 3238, 3239) represents one segmentwhose index s2 (0, . . . , 39) is shown above the block in rectangularregion 3240. Each block, e.g., block 3200 representing segment 0,conveys 8 information bits; each block comprises 8 rows corresponding tothe 8 bits in the segment, where the bits are listed from the mostsignificant bit to the least significant bit downwards from the top rowto the bottom row as shown in rectangular region 3243.

For an exemplary embodiment, the framing format shown in FIG. 32 is usedrepeatedly in every beaconslot, when the default mode of split-toneformat is used, with the following exception. In the first uplinksuperslot after the wireless terminal migrates to the ON state in thecurrent connection, the WT shall use the framing format shown in FIG.33. The first uplink superslot is defined: for a scenario when the WTmigrates to the ON state from the ACCESS state, for a scenario when theWT migrates to the ON state from a HOLD state, and for a scenario whenthe WT migrates to the ON state from the ON state of another connection.

FIG. 33 illustrates an exemplary definition of the default mode in thesplit-tone format of the uplink DCCH segments in the first uplinksuperslot after the WT migrates to the ON state. Drawing 3399 includesfive successive segments (3300, 3301, 3302, 3303, 3304) corresponding tosegment index numbers, s2=(0, 1, 2, 3, 4,), respectively in thesuperslot as indicated by rectangle 3306 above the segments. Each block,e.g., block 3300 representing segment 0 of the superslot, conveys 8information bits; each block comprises 8 rows corresponding to the 8bits in the segment, where the bits are listed from the most significantbit to the least significant bit downwards from the top row to thebottom row as shown in rectangular region 3308.

In the exemplary embodiment, in the scenario of migrating from the HOLDto ON state, the WT starts to transmit the uplink DCCH channel from thebeginning of the first UL superslot, and therefore the first uplink DCCHsegment shall transport the information bits in the leftmost informationcolumn of FIG. 33, the information bits of segment 3300. In theexemplary embodiment, in the scenario of migrating from the ACCESS stateto the ON state, the WT does not necessarily start from the beginning ofthe first UL superslot, but does still transmit the uplink DCCH segmentsaccording to the framing format specified in FIG. 33. For example, ifthe WT starts to transmit the UL DCCH segments from the halfslot of thesuperslot with index=10, then the WT skips the leftmost informationcolumn of FIG. 33 (segment 3300) and the first uplink segmenttransported corresponds to segment 3303). Note that in the exemplaryembodiment, superslot indexed halfslots (1-3) correspond to one segmentand superslot indexed halfslots (10-12) correspond to the next segmentfor the WT. In the exemplary embodiment, for the scenario of switchingbetween the full-tone and split-tone formats, the WT uses the framingformat shown in FIG. 32 without the above exception of using the formatshown in FIG. 33.

Once, the first UL superslot ends, the uplink DCCH channel segmentsswitch to the framing format of FIG. 32. Depending on where the firstuplink superslot ends, the point of switching the framing format may ormay not be the beginning of a beaconslot. Note that in this exemplaryembodiment, there are five DCCH segments for a given DCCH tone for asuperslot. For example, suppose that the first uplink superslot is ofuplink beaconslot superslot index=2, where beaconslot superslot indexrange is from 0 to 7 (superslot 0, superslot 1, . . . , superslot 7).Subsequently in the next uplink superslot, which is of uplink beaconslotsuperslot index=3, the first uplink DCCH segment using the defaultframing format of FIG. 32 is of index s2=15 (segment 3215 of FIG. 32)and transports the information corresponding to segment s2=15 (segment3215 of FIG. 32).

Each uplink DCCH segment is used to transmit a set of Dedicated ControlChannel Reports (DCRs). An exemplary summary list of DCRs in thesplit-tone format for the default mode is given in table 3400 FIG. 34.The information of table 3400 is applicable to the partitioned segmentsof FIGS. 32 and 33. Each segment of FIGS. 32 and 33 includes two or morereports as described in table 3400. First column 3402 of table 3400describes abbreviated names used for each exemplary report. The name ofeach report ends with a number which specifies the number of bits of theDCR. Second column 3404 of table 3400 briefly describes each namedreport. Third column 3406 specifies the segment index s2 of FIG. 32, inwhich a DCR is to be transmitted, and corresponds to a mapping betweentable 3400 and FIG. 32.

It should be noted that FIGS. 32, 33 and 34 describe the segments(indexed segments 0, 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, and 36)corresponding to a first WT in split tone format for default mode. Withrespect to FIG. 32, a second wireless terminal that use the split toneformat of default mode on the same logical tone in the DCCH will followthe same report pattern but the segments will be shifted by one, thusthe second WT uses indexed segments (1, 4, 7, 10, 13, 16, 19, 22, 25,28, 31, 34, and 37). With respect to FIG. 33, a second wireless terminalthat use the split tone format of default mode on the same logical tonein the DCCH will follow the same report pattern but the segments will beshifted by one, thus the second WT uses indexed segments 3301 and 3304.With respect to FIG. 32, a third wireless terminal that use the splittone format of default mode on the same logical tone in the DCCH willfollow the same report pattern but the segments will be shifted by two,thus the third WT uses indexed segments (2, 5, 8, 11, 14, 17, 20, 23,26, 29, 33, 35, and 38). With respect to FIG. 33, a third wirelessterminal that use the split tone format of default mode on the samelogical tone in the DCCH will follow the same report pattern but thesegments will be shifted by two, thus the third WT uses indexed segments3305. In FIG. 32, segment with index=39 is reserved.

FIG. 33 provides a representation corresponding to the replacement ofthe first superslot of a beaconslot corresponding to table 3299, e.g.,segment 3300 replaces segment 3200 and/or segment 3303 replaces segment3203. In FIG. 32, for each superslot, one or two segments are allocatedto an exemplary wireless terminal using split-tone DCCH format, and thelocation of the allocated segments varies depending on the superslot ofthe beaconslot. For example, in the first superslot, two segments (3200,3203) are allocated corresponding to the first and fourth DCCH segmentsof the superslots; in the second superslot, two segments (3206, 3209)are allocated corresponding to the 2^(nd) and 5th DCCH segments of thesuperslot; in the third superslot, one segment 3213 is allocatedcorresponding to the third DCCH segment of the superslot. In someembodiments, segment 3300, when used, is used to replace the firstscheduled DCCH segment of a superslot and segment 3303, when used, isused to replace the second scheduled DCCH segment of a superslot. Forexample, segment 3300 may replace segment 3206 and/or segment 3303 mayreplace segment 3309. As another example, segment 3300 may replacesegment 3212.

In some embodiments, the 5 bit absolute report of DL SNR (DLSNR5)follows the same format in split-tone format default mode as used in thefull-tone format default mode. In some such embodiments, there is anexception such that the default value of NumConsecutivePreferred isdifferent in the split-tone format than in the full-tone format, e.g., 6in the split tone format default mode vs 10 in the full tone formatdefault mode.

In some embodiments, the 3 bit DLDSNR3 report follows the same format inthe split-tone format default mode as used in the full-tone formatdefault mode. In some embodiments, the 4 bit DLSSNR4 report follows thesame format in the split-tone format default mode as used in thefull-tone format default mode.

In some embodiments, the 4 bit uplink transmission backoff report(ULTxBKF4) of the split tone format default mode is generated similarlyto the ULTxBKF5 of full tone format default mode, except table 3500 ofFIG. 35 is used for the report.

FIG. 35 is a table 3500 identifying bit format and interpretationsassociated with each of 16 bit patterns for an exemplary 4 bit uplinktransmission backoff report (ULTxBKF4), in accordance with variousembodiments. First column 3502 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column3504 identifies the reported WT uplink DCCH Backoff report values in dBscorresponding to each bit pattern each bit pattern. In this exemplaryembodiment 16 distinct levels can be reported ranging from 6 dB to 36dBs. A wireless terminal calculates wtULDCCHBackoff, e.g., as indicatedabove, selects the closest entry in table 3500 and uses that bit patternfor the report.

In some embodiments, the 4 bit DLBNR4 report follows the same format inthe split-tone format default mode as used in the full-tone formatdefault mode. In some embodiments, the 3 bit ULRQST3 report follows thesame format in the split-tone format default mode as used in thefull-tone format default mode. In some embodiments, the 4 bit ULRQST4report follows the same format in the split-tone format default mode asused in the full-tone format default mode.

In various embodiments, a flexible report is included in the DCCH in thesplit-tone format in the default mode, such that the WT decides whichtype of report to communicate and, the type of report can change fromone flexible reporting opportunity to the next for a given WT using itsallocated dedicated control channel segments.

In an exemplary embodiment, the WT uses a 1 bit type report (TYPE1) toindicate the type of report selected by the WT to be communicated in a 4bit body report (BODY4) of the same DCCH segment including both theTYPE1 and BODY4 reports. Table 3600 of FIG. 36 is an example of mappingbetween TYPE1 report information bits and the type of report carried bythe corresponding BODY4 report. First column 3602 indicates the twopossible bit patterns for the 1 bit TYPE1 report. Second column 3604indicates the type of report to be carried in the BODY4 report of thesame uplink dedicated control channel segment corresponding to the TYPE1 report. Table 3600 indicates that: bit pattern 0 indicates that BODY4report will be an ULRQST4 report, Bit pattern 01 indicates the BODY4report will be a Reserved report.

In some embodiments, a WT selects the TYPE1 and BODY4 reports byassessing the relative importance if the different types of reports fromamong which the selection may occur, e.g., the reports listed in table3600. In some embodiments, the WT can select the TYPE1 independentlyfrom one segment to another.

In some embodiments, the encoding and modulation scheme used when theuplink dedicated control channel segment uses the full-tone format isdifferent than the encoding and modulation scheme used when the uplinkdedicated control channel segment uses the split-tone format.

An exemplary first method used for encoding and modulation when thededicated control channel segment uses the full-tone format will now bedescribed. Let b₅, b₄, b₃, b₂, b₁, and b₀ denote the information bits tobe transmitted in the uplink dedicated control channel segment, where b₅is the most significant bit and b₀ is the least significant bit. Definec₂c₁c₀=(b₅b₄b₃).^(b₂b₁b₀), where .^ is a bit-wise logical OR operation.The WT determines a group of seven modulation-symbols from informationbit groups b₅b₄b₃ according to Table 3700 of FIG. 37. Table 3700 is anexemplary specification of uplink dedicated control channel segmentmodulation coding in full-tone format. First column 3702 of table 3700includes bit patterns for 3 ordered information bits; second column 3704includes corresponding sets of seven ordered coded modulation symbols,each set corresponding to a different possible bit pattern.

The seven modulation-symbols determined from b₅b₄b₃ are to be the sevenmost significant coded modulation-symbols of the output of the codingand modulation operation.

The WT determines a group of seven modulation-symbols from informationbit groups b₂ b₁ b₀ similarly using table 3700, and uses the sevenmodulation-symbols obtained as the next most significant codedmodulation-symbols of the output of the encoding and modulationoperation.

The WT determines a group of seven modulation-symbols from informationbit groups c₂c₁c₀ similarly using table 3700, and use the sevenmodulation-symbols obtained as the least significant codedmodulation-symbols of the output of the coding and modulation operation.

An exemplary second method used for encoding and modulation when thededicated control channel segment uses the split-tone format will now bedescribed. Let b₇, b₆, b₅, b₄, b₃, b₂, b₁, and b₀ denote the informationbits to be transmitted in the uplink dedicated control channel segment,where b7 is the most significant bit and b₀ is the least significantbit. Define c₃c₂c₁c₀=(b₇b₆b₅b₄).^(b₃b₂b₁b₀), where .^ is a bit-wiselogical OR operation. The WT determines a group of sevenmodulation-symbols from information bit groups b₇b₆b₅b₄ according toTable 3800 of FIG. 38. Table 3800 is an exemplary specification ofuplink dedicated control channel segment modulation coding in split-toneformat. First column 3802 of table 3800 includes bit patterns for 4ordered information bits; second column 3804 includes corresponding setsof seven ordered coded modulation symbols, each set corresponding to adifferent possible bit pattern.

The seven modulation-symbols determined from b₇b₆b₅b₄ are to be theseven most significant coded modulation-symbols of the output of thecoding and modulation operation.

The WT determines a group of seven modulation-symbols from informationbit groups b₃b₂ b₁ b₀ similarly using table 3800, and uses the sevenmodulation-symbols obtained as the next most significant codedmodulation-symbols of the output of the encoding and modulationoperation.

The WT determines a group of seven modulation-symbols from informationbit groups c₃c₂c₁c₀ similarly using table 3800, and uses the sevenmodulation-symbols obtained as the least significant codedmodulation-symbols of the output of the coding and modulation operation.

FIG. 39 is a drawing of a table 3900 illustrating exemplary wirelessterminal uplink traffic channel frame request group queue countinformation. Each wireless terminal maintains and updates its requestgroup count information. In this exemplary embodiment there are fourrequest groups (RG0, RG1, RG2, RG3). Other embodiments may use differentnumbers of request groups. In some embodiments, different WTs in thesystem may have different numbers of request groups. First column 3902lists queue element index and second column 3904 lists queue elementvalue. First row 3906 indicates that N[0]=the number of MAC frames thatthe WT intends to transmit for request group 0 (RG0); second row 3908indicates that N[1]=the number of MAC frames that the WT intends totransmit for request group 1 (RG1); third row indicates that N[2]=thenumber of MAC frames that the WT intends to transmit for request group2; fourth row 3912 indicates that N[3]=the number of MAC frames that theWT intends to transmit for request group 3.

Drawing 4000 of FIG. 40 includes an exemplary set of four request groupqueues (4002, 4004, 4006, 4008) being maintained by a wireless terminal,in accordance with an exemplary embodiment. Queue 0 4002 is the queuefor request group 0 information. Queue 0 information 4002 includes acount of the total number of frames, e.g., MAC frames, of queue 0traffic (N[0]) that the WT intends to transmit 4010 and thecorresponding frames of uplink traffic (frame 1 4012, frame 2, 4014,frame 3 4016, . . . , frame N₀ 4018). Queue 1 4004 is the queue forrequest group 1 information. Queue 1 information 4004 includes a countof the total number of frames, e.g., MAC frames, of queue 1 traffic(N[1]) that the WT intends to transmit 4020 and the corresponding framesof uplink traffic (frame 1 4022, frame 2, 4024, frame 3 4026, . . . ,frame N₁ 4028). Queue 2 4006 is the queue for request group 2information. Queue 2 information 4006 includes a count of the totalnumber of frames, e.g., MAC frames, of queue 2 traffic (N[2]) that theWT intends to transmit 4030 and the corresponding frames of uplinktraffic (frame 1 4032, frame 2, 4034, frame 3 4036, . . . , frame N₂4038). Queue 3 4008 is the queue for request group 3 information. Queue3 information 4008 includes a count of the total number of frames, e.g.,MAC frames, of queue 3 traffic (N[3]) that the WT intends to transmit4040 and the corresponding frames of uplink traffic (frame 1 4042, frame2, 4044, frame 3 4046, . . . , frame N₃ 4048). In some embodiments, therequest queues, for at least some wireless terminals, are priorityqueues. For example, in some embodiments, request group 0 queue 4002 isused for the highest priority traffic, request group 1 queue 4004 isused for the 2^(nd) highest priority traffic, request group 2 queue 4006is used for the third highest priority traffic, and request group 3queue 4008 is used for the lowest priority traffic, from the perspectiveof the individual wireless terminal.

In some embodiments, the traffic in at least some request queues duringat least some times for at least some wireless terminals have differentpriorities. In some embodiments, priority is one factor considered whenmapping a traffic flow to a request queue. In some embodiments, priorityis one factor considered when scheduling/transmitting traffic. In someembodiments, priority is representative of relative importance. In someembodiments, all other factors being equal, traffic belonging to ahigher priority is scheduled/transmitted more often than trafficbelonging to lower priorities.

Drawing 4052 of FIG. 40 illustrates exemplary mapping for a first WT, WTA, of uplink data stream traffic flows to its request group queues.First column 4054 includes information type of the data stream trafficflow; second column 4056 includes the identified queue (request group);third column 4058 includes comments. First row 4060 indicates thatcontrol information is mapped to request group 0 queue. Flows mapped tothe request group 0 queue are considered high priority, have strictlatency requirements, require low latency and/or have low bandwidthrequirements. Second row 4062 indicates that voice information is mappedto request group 1 queue. Flows mapped to the request group 1 queue alsorequire low latency but have a lower priority level than request group0. Third row 4064 indicates that gaming and audio stream application Ais mapped to request group 2 queue. For flows mapped to the requestgroup 2, latency is somewhat important and the bandwidth requirementsare slightly higher than for voice. Fourth row 4066 indicates that FTP,web browsing, and video stream application A are mapped to request group3 queue. Flows mapped to the request group 3, are delay insensitiveand/or require high bandwidth.

Drawing 4072 of FIG. 40 illustrates exemplary mapping for a second WT,WTB, of uplink data stream traffic flows to its request group queues.First column 4074 includes information type of the data stream trafficflow; second column 4076 includes the identified queue (request group);third column 4078 includes comments. First row 4080 indicates thatcontrol information is mapped to request group 0 queue. Flows mapped tothe request group 0 queue are considered high priority, have strictlatency requirements, require low latency and/or have low bandwidthrequirements. Second row 4082 indicates that voice and audio streamapplication A information are mapped to request group 1 queue. Flowsmapped to the request group 1 queue also require low latency but have alower priority level than request group 0. Third row 4084 indicates thatgaming and audio stream application B, and image stream application Aare mapped to request group 2 queue. For flows mapped to the requestgroup 2, latency is somewhat important and the bandwidth requirementsare slightly higher than for voice. Fourth row 4086 indicates that FTP,web browsing, and image stream application B are mapped to request group3 queue. Flows mapped to the request group 3, are delay insensitiveand/or require high bandwidth.

It should be noted the WT A and WT B use different mapping from theiruplink data stream traffic flows to their set of request group queues.For example audio stream application A is mapped to request group queue2 for WTA, while the same audio stream application A is mapped torequest group queue 1 for WTB. In addition, different WTs may havedifferent types of uplink data stream traffic flows. For example, WT Bincludes an audio stream application B that is not included for WT A.This approach, in accordance with various embodiments, allows each WT tocustomize and/or optimize its request queue mapping to match thedifferent types of data being communicated via its uplink trafficchannel segments. For example, a mobile node such as a voice and textmessage cell phone has different types of data streams than a mobiledata terminal used primarily for on-line gaming and web browsing, andwould typically have a different mapping of data streams to requestgroup queues.

In some embodiments, the mapping from uplink data stream traffic flowsto request group queues for a WT may change with time. Drawing 4001 ofFIG. 40A illustrates exemplary mapping for a WT C at a first time T1, ofuplink data stream traffic flows to its request group queues. Firstcolumn 4003 includes information type of the data stream traffic flow;second column 4005 includes the identified queue (request group); thirdcolumn 4007 includes comments. First row 4009 indicates that controlinformation is mapped to request group 0 queue. Flows mapped to therequest group 0 queue are considered high priority, have strict latencyrequirements, require low latency and/or have low bandwidthrequirements. Second row 4011 indicates that voice information is mappedto request group 1 queue. Flows mapped to the request group 1 queue alsorequire low latency but have a lower priority level than request group0. Third row 4013 indicates that gaming and audio stream application Ais mapped to request group 2 queue. For flows mapped to the requestgroup 2, latency is somewhat important and the bandwidth requirementsare slightly higher than for voice. Fourth row 4015 indicates that FTP,web browsing, and video stream application A are mapped to request group3 queue. Flows mapped to the request group 3, are delay insensitiveand/or require high bandwidth.

Drawing 4017 of FIG. 40A illustrates exemplary mapping for a WT C at asecond time T2, of uplink data stream traffic flows to its request groupqueues. First column 4019 includes information type of the data streamtraffic flow; second column 4021 includes the identified queue (requestgroup); third column 4023 includes comments. First row 4025 indicatesthat control information is mapped to request group 0 queue. Flowsmapped to the request group 0 queue are considered high priority, havestrict latency requirements, require low latency and/or have lowbandwidth requirements. Second row 4027 indicates that voice applicationand a gaming application is mapped to request group 1 queue. Flowsmapped to the request group 1 queue also require low latency but have alower priority level than request group 0. Third row 4029 indicates thatvideo streaming application A is mapped to request group 2 queue. Forflows mapped to the request group 2, latency is somewhat important andthe bandwidth requirements are slightly higher than for voice. Fourthrow 4031 indicates that FTP, web browsing and video streamingapplication B are mapped to request group 3 queue. Flows mapped to therequest group 3, are delay insensitive and/or require high bandwidth.

Drawing 4033 of FIG. 73 illustrates exemplary mapping for a WT C at athird time T3, of uplink data stream traffic flows to its request groupqueues. First column 4035 includes information type of the data streamtraffic flow; second column 4037 includes the identified queue (requestgroup); third column 4039 includes comments. First row 4041 indicatesthat control information is mapped to request group 0 queue. Flowsmapped to the request group 0 queue are considered high priority, havestrict latency requirements, require low latency and/or have lowbandwidth requirements. Second row 4043 and third row 4045 indicate thatno data traffic applications are mapped to request group 1 and requestgroup 2 queues, respectively. Fourth row 4047 indicates that FTP and webbrowsing are mapped to request group 3 queue. Flows mapped to therequest group 3, are delay insensitive and/or require high bandwidth.

It should be noted WT C uses different mappings from their uplink datastream traffic flows to their set of request group queues at the threetimes T1, T2 and T3. For example audio stream application A is mapped torequest group queue 2 at time T1, while the same audio streamapplication A is mapped to request group queue 1 at time T2. Inaddition, the WT may have different types of uplink data stream trafficflows at different times. For example, at time T2, the WT includes avideo stream application B that is not included at time T1. In addition,the WT may have no uplink data stream traffic flows mapped to a specificrequest group queue at a given time. For example, at time T3, there areno uplink data stream traffic flows that are mapped to request groupqueues 1 and 2. This approach, in accordance with various embodiments,allows each WT to customize and/or optimize its request queue mapping tomatch the different types of data being communicated via its uplinktraffic channel segments at any time.

FIG. 41 illustrates an exemplary request group queue structure, multiplerequest dictionaries, a plurality of types of uplink traffic channelrequest reports, and grouping of sets of queues in accordance withexemplary formats used for each of the types of reports. In thisexemplary embodiment, there are four request group queues for a givenwireless terminal. The exemplary structure accommodates four requestdictionaries. The exemplary structure uses three types of uplink trafficchannel request reports (a 1 bit report, a 3-bit report, and a 4-bitreport).

FIG. 41 includes: exemplary queue 0 (request group 0) information 4102which includes the total number of frames, e.g., MAC frames, of queue 0traffic that an exemplary WT intends to transmit (N[0]) 4110, exemplaryqueue 1 (request group 1) information 4104 which includes the totalnumber of frames, e.g., MAC frames, of queue 1 traffic that an exemplaryWT intends to transmit (N[1]) 4112, exemplary queue 2 (request group 2)information 4106 which includes the total number of frames, e.g., MACframes, of queue 2 traffic that an exemplary WT intends to transmit(N[2]) 4114, and exemplary queue 3 (request group 3) information 4108which includes the total number of frames, e.g., MAC frames, of queue 3traffic that an exemplary WT intends to transmit (N[3]) 4116. The set ofqueue 0 info 4102, queue 1 info 4104, queue 2 info 4106 and queue 3 info4108 correspond to one WT in the system. Each WT in the system maintainsits set of queues, tracking uplink traffic frames that it may intend totransmit.

Table 4118 identifies grouping of queue sets used by different types ofrequest reports as a function of the dictionary in use. Column 4120identifies the dictionary. The first type of exemplary report is, e.g.,a 1 bit information report. Column 4122 identifies the first set ofqueues used for first type reports. The first set of queues is the set{queue 0 and queue 1} for the first type of report irrespective of therequest dictionary. Column 4124 identifies the second set of queues usedfor second type reports. The second set of queues is the set {queue 0}for the second type of report irrespective of the request dictionary.Column 4126 identifies the third set of queues used for second typereports. The third set of queues is: (i) the set {queue 1, queue 2,queue 3} for the second type of report for request dictionary 0, (ii)the set of {queue 2} for the second type of report for requestdictionary 1, and (iii) the set of {queue 1} for the second type ofreport for dictionary 2 and 3. The third type of report uses a fourthand fifth set of queues for each dictionary. The third type of reportuses a sixth set of queues for dictionaries 1, 2, and 3. The third typeof report uses a seventh set of queues for dictionary 3. Column 4128identifies that the fourth set of queues for the third type of report isthe set {queue 0} irrespective of the dictionary. Column 4130 identifiesthat the fifth set of queues for the third type of report is the set{queue 1, queue 2, queue 3} for dictionary 0, the set {queue 2} fordictionary 1, the set {queue 1} for dictionaries 2 and 3. Column 4132identifies that the sixth set of queues for the third type of report isthe set {queue 1, queue 3} for dictionary 1, the set {queue 2, queue 3}for dictionary 2, and the set {queue 2} for dictionary 3. Column 4134identifies that the seventh set of queues for the third type of reportis the set {queue 3} for dictionary 3.

As an example, the (first, second, and third) types of reports may bethe exemplary (ULRQST1, ULRQST3, and ULRQST4) reports, respectively, ofFIGS. 16-25. The sets of queues used (See table 4118) will be describedwith respect to the dictionary 0 for the exemplary ULRQST1, ULRQST3, andULRQST 4. First set of queues {queue 0, queue 1} corresponds to ULRQST1using N[0]+N[1] in table 1600, e.g., an ULRQST1=1 indicates thatN[0]+N[1]>0. Queue stats of second set of queues {queue 0} and third setof queues {queue 1, queue 2, queue 3} are jointly coded in an ULRQST3.Second set of queues {queue 0} corresponds to an ULRQST3 which uses N[0]as the first jointly coded element in table 1900, e.g., an ULRQST3=001indicates N[0]=0. Third set of queues {queue 1, queue 2, queue 3}corresponds to an ULRQST3 which uses (N[1]+N[2]+N[3]) as the secondjointly coded element in table 1900, e.g., an ULRQST3=001 indicatesceil((N[1]+N[2]+N[3])/y)=1. Queue stats of fourth set of queues {queue0} or the fifth set of queues {queue 1, queue 2, queue 3} are coded inan ULRQST4. The fourth set of queues corresponds to ULRQST4 using N[0]in table 1800, e.g., an ULRQST4=0010 indicates that N[0]>=4. The fifthset of queues corresponds to ULRQST4 using N[1]+N[2]+N[3] in table 1800,e.g., an ULRQST4=0011 indicates ceil((N[1]+N[2]+N[3])/y)=1.

In the exemplary embodiment where (first type, second, and third) typesof reports are the exemplary (ULRQST1, ULRQST3, and ULRQST4) reports ofFIGS. 16-25, the first type of report is independent of requestdictionary and uses the first set of queues of table 4118, a second typeof report communicates queue stat information about both a second set ofqueues and a corresponding third set of queues from table 4118, and athird type of report communicates queue stat information about one of: afourth sets of queues, a corresponding fifth set of queues, acorresponding sixth set of queues, and a corresponding seventh set ofqueues.

FIG. 42, comprising the combination of FIG. 42A, FIG. 42B, FIG. 42C,FIG. 42D, and FIG. 42E is a flowchart 4200 of an exemplary method ofoperating a wireless terminal in accordance with various embodiments.Operation of the exemplary method starts in step 4202, where the WT ispowered on and initialized. Queue definition information 4204, e.g.,mapping information defining mapping of traffic flows from variousapplications into MAC frames of specific request group queues andvarious grouping of request groups into sets of request groups, and setsof request dictionary information 4206 are available for use by thewireless terminal. For example, the information 4204 and 4206 may bepre-stored in the wireless terminal in non-volatile memory. In someembodiments, a default request dictionary from among the plurality ofavailable request dictionaries is used by the wireless terminalinitially, e.g., request dictionary 0. Operation proceeds from startstep 4202 to steps 4208, 4210 and 4212.

In step 4208 the wireless terminal maintains transmission queue statsfor a plurality of queues, e.g., request group 0 queue, request group 1queue, request group 2 queue and request group 3 queue. Step 4208includes sub-step 4214 and sub-step 4216. In sub-step 4214, the wirelessterminal increments queue stats when data to be transmitted is added toa queue. For example, new packets from an uplink data stream flow, e.g.,a voice communications session flow, are mapped as MAC frames to one ofthe request groups, e.g., request group 1 queue and a queue stat, e.g.,N[1] representing the total number of request group 1 frames that the WTintends to transmit is updated. In some embodiments, different wirelessterminals use different mappings. In sub-step 4216, the WT decrementsthe queue stats when data to be transmitted is removed from a queue. Forexample, the data to be transmitted may be removed from the queuebecause the data has been transmitted, the data has been transmitted anda positive acknowledgement was received, the data no longer needs to betransmitted because a data validity timer has expired, or the data nolonger needs to be transmitted because the communications session hasbeen terminated.

In step 4210, the wireless terminal generates transmission poweravailability information. For example, the wireless terminal calculatesthe wireless terminal transmission backoff power, determines a wirelessterminal transmission backoff power report value, and stores backoffpower information. Step 4210 is performed on an ongoing basis with thestored information being updated, e.g., in accordance with a DCCHstructure.

In step 4212, the wireless terminal generates transmission path lossinformation for at least two physical attachment points. For example,the wireless terminal measures received pilot and/or beacon signals fromat least two physical attachment points calculates a ratio value,determines a beacon ratio report value, e.g., corresponding to a genericbeacon ratio report of a first or second type or a specific beacon ratioreport, and stores the beacon ratio report information. Step 4212 isperformed on an ongoing basis with the stored information being updated,e.g. in accordance with a DCCH structure.

In addition to performing step 4208, 4210 and 4212, the WT, for eachreporting opportunity in a (first, second, third) set of predeterminedtransmission queue stats reporting opportunities operation goes to(sub-routine 1 4224, sub-routine 2 4238, subroutine 3 4256), via (step4218, step 4220, step 4222), respectively. For example, each first setof predetermined transmission queue stat reporting opportunitiescorresponds to each one-bit uplink traffic channel request reportingopportunity in the timing structure. For example, if a WT iscommunicating over DCCH segments using the full-tone DCCH format defaultmode, e.g., of FIG. 10, the WT receives 16 opportunities to send ULRQST1in a beaconslot. Continuing with the example, each second set ofpredetermined transmission queue stat reporting opportunitiescorresponds to each three-bit uplink traffic channel request reportingopportunity in the timing structure. For example, if a WT iscommunicating over DCCH segments using the full-tone DCCH format defaultmode, e.g., of FIG. 10, the WT receives 12 opportunities to send ULRQST3in a beaconslot. If a WT is communicating over DCCH segments using thesplit-tone DCCH format default mode, e.g., of FIG. 32, the WT receives 6opportunities to send ULRQST3 in a beaconslot. Continuing with theexample, each third set of predetermined transmission queue statreporting opportunities corresponds to each four-bit uplink trafficchannel request reporting opportunity in the timing structure. Forexample, if a WT is communicating over DCCH segments using the full-toneDCCH format default mode, e.g., of FIG. 10, the WT receives 9opportunities to send ULRQST4 in a beaconslot. If a WT is communicatingover DCCH segments using the split-tone DCCH format default mode, e.g.,of FIG. 32, the WT receives 6 opportunities to send ULRQST4 in abeaconslot. For each flexible report in which the WT decides to send anULRQST4, operation also goes to sub-routine 4256 via connecting node4222.

Exemplary traffic availability subroutine 1 4224 will now be described.Operation starts in step 4226, and the WT receives backlog informationfor a first set of queues, e.g. the set of {Queue 0, Queue 1} where theinformation received is N[0]+N[1]. Operation proceeds from step 4226 tostep 4230.

In step 4230, the WT checks if there is a backlog of traffic in thefirst set of queues. If there is no backlog in the first set of queues,N[0]+N[1]=0, then operation proceeds from step 4230 to step 4234, wherethe WT transmits a first number of information bits, e.g., 1 informationbit, indicating no traffic backlog in the first set of queues, e.g. theinformation bit is set equal to 0. Alternatively, if there is a backlogin the first set of queues, N[0]+N[1]>0, then operation proceeds fromstep 4230 to step 4232, where the WT transmits a first number ofinformation bits, e.g., 1 information bit, indicating a traffic backlogin the first set of queues, e.g. the information bit is set equal to 1.Operation proceeds from either step 4232 or step 4234 to return step4236.

Exemplary traffic availability subroutine 2 4238 will now be described.Operation starts in step 4240, and the WT receives backlog informationfor a second set of queues, e.g. the set of {Queue 0} where theinformation received is N[0]. In step 4240, the WT also receives backloginformation for a third set of queues, e.g., the set {queue 1, queue2,queue3} or {queue 2} or {queue 1} depending on the request dictionary inuse by the WT. For example, corresponding to dictionary (1, 2, 3, 4),the WT may receive (N[1]+N[2]+N[3], N[2], N[1], N[1]), respectively.Operation proceeds from step 4240 to step 4246.

In step 4246, the WT jointly encodes the backlog informationcorresponding to the second and third sets of queues into a secondpredetermined number of information bits, e.g., 3, said joint encodingoptionally including quantization. In some embodiments, for at leastsome request dictionaries sub-step 4248 and sub-step 4250 are performedas part of step 4246. In some embodiments, for at least some requestdictionaries for at least some iterations of step 4246, sub-step 4248and sub-step 4250 are performed as part of step 4246. Sub-step 4248directs operation to a quantization level control factor subroutine.Sub-step 4250 calculates a quantization level as a function of adetermined control factor. For example, consider exemplary ULRQST3 usingdefault request dictionary 0 as shown in FIG. 19. In that exemplary caseeach of the quantization levels are calculated as a function of controlfactor y. In such an exemplary embodiment, sub-steps 4248 and 4250 areperformed in determining the information bit pattern to place in theULRQST3 report. Alternatively, consider exemplary ULRQST3 using requestdictionary 1 as shown in FIG. 21. In that case, none of the quantizationlevels are calculated as a function of a control factor, e.g. y or z,and therefore sub-step 4248 and 4250 are not performed.

Operation proceeds from step 4246 to step 4252, where the WT transmitsthe jointly coded backlog information for the second and third sets ofqueues using the second predetermined number of information bits, e.g.,3 information bits. Operation proceeds from step 4252 to return step4254.

Exemplary traffic availability subroutine 3 4256 will now be described.Operation starts in step 4258, and the WT receives backlog informationfor a fourth set of queues, e.g. the set of {Queue 0} where theinformation received is N[0]. In step 4240, the WT also receives backloginformation for a fifth set of queues, e.g., the set {queue 1, queue2,queue3} or {queue 2} or {queue 1} depending on the request dictionary inuse by the WT. For example, corresponding to dictionary (0, 1, 2, 3),the WT may receive (N[1]+N[2]+N[3], N[2], N[1], N[1]), respectively. Instep 4240, the WT may also receives backlog information for a sixth setof queues, e.g., the set {queue 1, queue3} or {queue 2, queue3} or{queue 2} depending on the request dictionary in use by the WT. Forexample, corresponding to dictionary (1, 2, 3), the WT may receive(N[1]+N[3], N[2]+N[3], N[2]), respectively. In step 4240, the WT mayalso receive backlog information for a seventh set of queues, e.g., theset {queue 3} if request dictionary 3 is in use by the WT. Operationproceeds from step 4258 to step 4266.

In step 4268, the WT encodes the backlog information corresponding toone of the fourth, fifth, sixth, and seventh sets of queues into a thirdpredetermined number of information bits, e.g., 4, said encodingoptionally including quantization. In some embodiments, for at leastsome request dictionaries sub-step 4270 and sub-step 4272 are performedas part of step 4268. In some embodiments, for at least some requestdictionaries for at least some iterations of step 4268, sub-step 4270and sub-step 4272 are performed as part of step 4268. Sub-step 4270directs operation to a quantization level control factor subroutine.Sub-step 4272 calculates a quantization level as a function of adetermined control factor.

Operation proceeds from step 4268 to step 4274, where the WT transmitsthe coded backlog information for one of the fourth, fifth, sixth, andseventh sets of queues using the third predetermined number ofinformation bits, e.g., 4 information bits. Operation proceeds from step4274 to return step 4276.

Exemplary quantization level control factor subroutine 4278 will now bedescribed. In some embodiments, the exemplary quantization level controlfactor subroutine 4278 implementation includes the use of table 1700 ofFIG. 17. First column 1702 lists a condition; second column 1704 liststhe corresponding value of output control parameter y; third column 1706lists the corresponding value of output control parameter Z. Operationstarts in step 4279, and the subroutine receives power information 4280,e.g., the last DCCH transmitter power backoff report, and path lossinformation 4282, e.g., the last reported beacon ratio report. Operationproceeds from step 4279 to step 4284, where the WT checks as to whetheror not the power information and path loss information satisfy a firstcriteria. For example, the first criteria is in an exemplary embodiment:(x>28) AND (b>=9), where x is the value in dBs of the most recent uplinktransmission power backoff report, e.g., ULTxBKF5 and b is the value indBs of the most recent downlink beacon ratio report, e.g., DLBNR4. Ifthe first criteria is satisfied, then operation proceeds from step 4284to step 4286; however if the first criteria is not satisfied, operationproceeds to step 4288.

In step 4286, the wireless terminal sets control factors, e.g. the set{Y, Z}, to a first predetermined set of values, e.g., Y=Y1, Z=Z1, whereY1 and Z1 are positive integers. In one exemplary embodiment, Y1=2 andZ1=10.

Returning to step 4288, in step 4288 the WT checks as to whether or notthe power information and path loss information satisfy a secondcriteria. For example in an exemplary embodiment, the second criteria is(x>27) AND (b>=8). If the second criteria is satisfied, then operationproceeds from step 4288 to step 4290, where the wireless terminal setscontrol factors, e.g. the set {Y, Z}, to a second predetermined set ofvalues, e.g., Y=Y2, Z=Z2, where Y2 and Z2 are positive integers. In oneexemplary embodiment, Y2=2 and Z2=9. If the second criteria is notsatisfied operation proceeds to another criteria checking step where,depending on whether or not the criteria is satisfied, the controlfactor are set to predetermined values or testing is continued.

There are a fixed number of test criteria, utilized in the quantizationlevel control factor subroutine. If none of the first N−1 test criteriaare satisfied, operation proceeds to step 4292, where the wirelessterminal tests as to whether or not the power information and path lossinformation satisfy an Nth criteria. For example in an exemplaryembodiment where N=9, the Nth criteria is (x>12) and (b<−5). If the Nthcriteria is satisfied, then operation proceeds from step 4292 to step4294, where the wireless terminal sets control factors, e.g. the set {Y,Z}, to a Nth predetermined set of values, e.g., Y=YN, Z=ZN, where YN andZN are positive integers. In one exemplary embodiment, YN=1 and ZN=2. Ifthe Nth criteria is not satisfied, the wireless terminal sets controlfactors, e.g., the set {Y, Z} to a (N+1)th predetermined set of values,e.g., a default set Y=YD, Z=ZD, where YD and ZD are positive integers.In one exemplary embodiment, YD=1 and ZD=1.

Operation proceeds from step 4286, step 4290, other control factorsetting steps, step 4294 or step 4296 to step 4298. In step 4298, the WTreturns at least one control factor value, e.g., Y and/or Z.

FIG. 43 is a flowchart 4300 of an exemplary method of operating awireless terminal in accordance with various embodiments. Operationstarts in step 4302, where the wireless terminal is powered on,initialized, has established a connection with a base station. Operationproceeds from start step 4302 to step 4304.

In step 4304, the wireless terminal determines whether the WT isoperating in a full-tone format DCCH mode or a split-tone format DCCHmode. For each DCCH segment allocated to the WT in full-tone format DCCHmode, the WT proceeds from step 4304 to step 4306. For each DCCH segmentallocated to the WT in split-tone format DCCH mode, the WT proceeds fromstep 4304 to step 4308.

In step 4306, the WT determines a set of 21 coded modulation-symbolvalues from 6 information bits (b5, b4, b3, b2, b1, b0). Step 4306includes sub-steps 4312, 4314, 4316, and 4318. In sub-step 4312, the WTdetermines 3 additional bits (c2, c1, c0) as a function of the 6information bits. For example, in one exemplary embodiment,c2c11c0=(b5b4b3).^(b2b1b0) where .^ is a bit wise exclusive ORoperation. Operation proceeds from step 4312 to step 4314. In sub-step4314, the WT determines the seven most-significant modulation symbolsusing a first mapping function and 3 bits (b5, b4, b3) as input.Operation proceeds from sub-step 4314 to sub-step 4316. In sub-step4316, the WT determines the seven next most significant modulationsymbols using the first mapping function and 3 bits (b2, b1, b0) asinput. Operation proceeds from sub-step 4316 to sub-step 4318. Insub-step 4318, the WT determines the seven least-significant modulationsymbol using the first mapping function and 3 bits (c2, c1, c0) asinput.

In step 4308, the WT determines a set of 21 coded modulation-symbolvalues from 8 information bits (b7, b6, b5, b4, b3, b2, b1, b0). Step4308 includes sub-steps 4320, 4322, 4324, and 4326. In sub-step 4320,the WT determines 4 additional bits (c3, c2, c1, c0) as a function ofthe 8 information bits. For example, in one exemplary embodiment,c3c2c1c0=(b7b6b5b4).^(b3b2b1b0) where .^ is a bit wise exclusive ORoperation. Operation proceeds from step 4320 to step 4322. In sub-step4322, the WT determines the seven most-significant modulation symbolsusing a second mapping function and 4 bits (b7, b6, b5, b4) as input.Operation proceeds from sub-step 4322 to sub-step 4324. In sub-step4324, the WT determines the seven next most significant modulationsymbols using the second mapping function and 4 bits (b3, b2, b1, b0) asinput. Operation proceeds from sub-step 4324 to sub-step 4326. Insub-step 4326, the WT determines the seven least-significant modulationsymbol using the second mapping function and 4 bits (c3, c2, c1, c0) asinput.

For each DCCH segment allocated to the wireless terminal, operationproceeds from either step 4306 or step 4308 to step 4310. In step 4310,the wireless terminal transmits the twenty-one determined modulationsymbols of the segment.

In some embodiments, each DCCH segment corresponds to 21 OFDM tonesymbols each tone-symbol of the DCCH segment using the same singlelogical tone in the uplink timing and frequency structure. The logicaltone may be hopped during a DCCH segment, e.g., the same logical tonemay corresponds to three different physical tones in the uplink toneblock being used for the connection, with each physical tone remainingthe same for seven successive OFDM symbol transmission time periods.

In one exemplary embodiment, each segment corresponds to multiple DCCHreports. In one exemplary embodiment, the first mapping function isrepresented by table 3700 of FIG. 37, and the second mapping function isrepresented by table 3800 of FIG. 38.

FIG. 44 is a flowchart 4400 of an exemplary method of operating awireless terminal to report control information in accordance withvarious embodiments. Operation starts in step 4402, where the wirelessterminal is powered up and initialized. Operation proceeds from startstep 4402 to step 4404. In step 4404, the WT checks as to whether or notone of the following has occurred: (i) a transition from a first mode ofWT operation to a second mode of WT operation and (ii) a handoffoperation from a first connection to a second connection while remainingin the second mode of operation. In some embodiments, the second mode ofoperation is an ON mode of operation and said first mode of operation isone of a hold mode of operation, a sleep mode of operation, and anACCESS mode of operation. In some embodiments, during the ON mode ofoperation, the wireless terminal can transmit user data on an uplink andduring the hold and sleep modes of operation the wireless terminal isprecluded from transmitting user data on said uplink. If one of theconditions checked for in step 4404 has occurred, operation proceeds tostep 4406; otherwise, operation proceeds back to step 4404 where thechecks are again performed.

In step 4406, the WT transmits an initial control information reportset, said transmission of the initial control information report sethaving a first duration equal to a first time period. In someembodiments, the initial control information report set can include oneor a plurality of reports. Operation proceeds from step 4406 to step4408. In step 4408, the WT checks as to whether or not the WT is in the2^(nd) mode of operation. If the WT is in the second mode of operation,operation proceeds from step 4408 to step 4410; otherwise operationproceeds to step 4404.

In step 4410, the WT transmits a first additional control informationreport set, said transmission of the first additional controlinformation report set for a period of time which is the same as firsttime period, the first additional control information report set beingdifferent than from said initial control information report set. In someembodiments, the initial control information report set is differentfrom the first additional control information report set due to theinitial and first additional control information report sets havingdifferent formats. In some embodiments, the initial control informationreport set includes at least one report that is not included in thefirst additional control information report set. In some suchembodiments, the initial control information report set includes atleast two reports that are not included in the first additional controlinformation report set. In some embodiments, the at least one reportthat is not included in the first additional control information reportset is one of an interference report and a wireless terminaltransmission power availability report. Operation proceeds from step4410 to step 4412. In step 4412, the WT checks as to whether or not theWT is in the 2^(nd) mode of operation. If the WT is in the second modeof operation, operation proceeds from step 4412 to step 4414; otherwiseoperation proceeds to step 4404.

In step 4414, the WT transmits a second additional control informationreport set for a period of time which is the same as said first timeperiod, said second additional control information report including atleast one report that is not included in said first additional controlinformation report set. Operation proceeds from step 4414 to step 4416.In step 4416, the WT checks as to whether or not the WT is in the 2^(nd)mode of operation. If the WT is in the second mode of operation,operation proceeds from step 4416 to step 4410; otherwise operationproceeds to step 4404.

FIGS. 45 and 46 are used to illustrate an exemplary embodiment. FIGS. 45and 46 are applicable to some embodiments discussed with respect toflowchart 4400 of FIG. 44. Drawing 4500 of FIG. 45 includes a initialcontrol information report set 4502, followed by a first additionalcontrol information report set 4504, followed by a second additionalcontrol information report set 4506, followed by a 2^(nd) iteration offirst additional control information report set 4508, followed by a2^(nd) iteration of second additional control information 4510. Eachcontrol information report set (4502, 4504, 4506, 4508, 4510) has acorresponding transmission time period (4512, 4514, 4516, 4518, 4520),respectively, where the duration of each of the time periods (4512,4514, 4516, 4518, 4520) is the same, the duration being 105 OFDM symboltransmission time periods.

Dotted line 4522 indicates that an event occurred slightly previous tothe transmission of the initial control information report settransmission, the event being one of (i) a mode transition from anaccess mode as indicated by block 4524 to an ON state as indicated byblock 4526, (ii) a mode transition from a HOLD state as indicated byblock 4528 to an ON state as indicated by block 4530, and (iii) ahandoff operation from a first connection in an ON state as indicated byblock 4532 to a second connection in an ON state as indicated by block4534.

As an example, initial control information report set 4502, firstadditional control information report set 4504 and second controlinformation report set 4506 may be communicated during a firstbeaconslot, while 2^(nd) iteration of first additional controlinformation report set 4508 and 2^(nd) iteration of second additionalcontrol information report set 4510 may be communicated during the nextbeaconslot. Continuing with the example, each information report set maycorrespond to a superslot within the beaconslot. For example, using thestructure described with respect to the full-tone format of the DCCH fora wireless terminal of FIGS. 10 and 11, one possible mapping of segmentscorresponding to FIG. 45 is the following. The initial controlinformation report set corresponds to FIG. 11; the first additionalcontrol information report set corresponding to indexed segments 30-34of the beaconslot; the second additional control information setcorresponds to indexed segments 30-39 of the beaconslot. FIG. 45describes such an exemplary mapping.

Drawing 4600 of FIG. 46 describes the format of an exemplary initialcontrol information report set. First column 4602 identifies the bitdefinition (5, 4, 3, 2, 1, 0). Second column 4604 identifies that thefirst segment includes a RSVD2 report and a ULRQST4 report. Third column4606 identifies that the second segment includes a DLSNR5 report and anULRQST1 report. Fourth column 4608 identifies that the third segmentincludes a DLSSNR4 report, a RSVD1 report, and an ULRQST1 report. Fifthcolumn 4610 identifies that the fourth segment includes a DLBNR4 report,a RSVD1 report, and a ULRQST1 report. Sixth column 4612 identifies thatthe fifth segment includes an ULTXBKF5 report and an ULRQST1 report.

Drawing 4630 describes the format of an exemplary 1^(st) additionalcontrol information report set. First column 4632 identifies the bitdefinition (5, 4, 3, 2, 1, 0). Second column 4634 identifies the firstsegment includes a DLSNR5 report and a ULRQST1 report. Third column 4636identifies that the second segment includes a RSVD2 report and anULRQST4 report. Fourth column 4638 identifies that the third segmentincludes a DLDSNR3 report and an ULRQST3 report. Fifth column 4640identifies that the fourth segment includes a DLSNR5 report and aULRQST1 report. Sixth column 4642 identifies that the sixth segmentincludes an RSVD2 report and an ULRQST4 report.

Drawing 4660 describes the format of an exemplary 2^(nd) additionalcontrol information report set. First column 4662 identifies the bitdefinition (5, 4, 3, 2, 1, 0). Second column 4664 identifies the firstsegment includes a DLDSNR3 report and a ULRQST3 report. Third column4666 identifies that the second segment includes a DLSSNR4 report, aRSVD1 report and an ULRQST1 report. Fourth column 4668 identifies thatthe third segment includes a DLSNR5 report and an ULRQST1 report. Fifthcolumn 4670 identifies that the fourth segment includes a RSVD2 reportand a ULRQST4 report. Sixth column 4672 identifies that the sixthsegment includes a DLDSNR3 report and an ULRQST3 report.

It can be observed in FIG. 46 that the initial and first additionalreports sets will be different because they use different formats. Itcan also be seen that the initial control information report setincludes at least two reports, DLBNR4 and ULTXBKF5, that are notincluded in the first additional control information report set. TheDLBNR4 is an interference report and the ULTXBKF5 is a wireless terminalpower availability report. In the example of FIG. 46, the secondadditional report includes at least one additional report that is notincluded in the first additional report, RSVD1 report.

FIG. 47 is a flowchart 4700 of an exemplary method of operating acommunications device in accordance with various embodiments; thecommunications device including information indicating a predeterminedreport sequence for use in controlling the transmission of a pluralityof different control information reports on a recurring basis. In someembodiments, the communications device is a wireless terminal, e.g., amobile node. For example, the wireless terminal may be one of aplurality of wireless terminals in a multiple access orthogonalfrequency division multiplexing (OFDM) wireless communications system.

Operation starts in step 4702, and proceeds to step 4704. In step 4704the communications device checks as to whether or at least one of thefollowing has occurred: (i) a transition from a first mode ofcommunications device operation to a second mode of communicationsdevice operation and (ii) a handoff operation from a first connection,e.g., with a first base station sector physical attachment point, to asecond connection, e.g., with a second base station sector physicalattachment point, while remaining in the second mode of communicationsdevice operation. In some embodiments, the second mode of communicationsdevice operation is an ON mode of operation, and the first mode ofoperation is one of a hold mode of operation and a sleep mode ofoperation. In some such embodiments, the communications device cantransmit user data on an uplink during the ON mode of operation and isprecluded from transmitting user data on the uplink during the hold andsleep modes of operation.

If at least one of the tested conditions of step 4704 was satisfied,then operation proceeds from step 4704 to either step 4706 or step 4708depending upon the embodiment. Step 4706 is an optional step included insome embodiments, but omitted in other embodiments.

Step 4706 is included in some embodiments where the communicationsdevice supports a plurality of different initial condition controlinformation report sets. In step 4706, the communications device selectswhich one of the plurality of initial control information report sets totransmit as a function of the portion of the sequence to be replaced.Operation proceeds from step 4706 to step 4708.

In step 4708, the communications device transmits an initial controlinformation report set. In various embodiments, transmitting an initialcontrol information report set includes transmitting at least one reportwhich would not have been transmitted during the time period used totransmit the initial report if the transmitted reports had followed thepredetermined sequence. For example, for a given initial report the atleast one report which would not have been transmitted during the timeperiod used to transmit the initial report if the transmitted reportshad followed the predetermined sequence is one of an interferencereport, e.g., a beacon ratio report, and a communications devicetransmission power availability report, e.g., a communications devicetransmitter power backoff report. In various embodiments, the initialcontrol information report set can include one or a plurality ofreports. In some embodiments, transmitting an initial controlinformation report set includes transmitting said initial controlinformation report set on a dedicated uplink control channel. In somesuch embodiments, the dedicated uplink control channel is a single tonechannel. In some such embodiments, the single tone of the single tonechannel is hopped over time, e.g., the single logical channel tonechanges to different physical tones due to tone hopping. In variousembodiments, the predetermined report sequence repeats over a timeperiod which is greater than a transmission time period used to transmitsaid initial report set. For example, in an exemplary embodiment, apredetermined reporting sequence repeats on a beaconslot basis, with abeaconslot being 912 OFDM symbol transmission time interval periods,while an exemplary time period used to transmit an initial report setmay be 105 OFDM symbol transmission time periods.

Operation proceeds from step 4708 to step 4710, where the communicationsdevice checks as to whether it is in the second mode of operation. Ifthe communications device is in the 2^(nd) mode of operation, operationproceeds to step 4712; otherwise, operation proceeds to step 4704. Instep 4712, the communications device transmits an additional controlinformation report set in accordance with the information indicated inthe predetermined reporting sequence. Operation proceeds from step 4712to step 4710.

In some embodiments, step 4712 following an initial control informationreport set transmission of step 4708 includes a first additional controlinformation report set, wherein the initial control information reportset includes at least one information report set that is not included inthe first additional control information report set. For example, the atleast one information report that is not included in said firstadditional control information report set is one of an interferencereport, e.g., a beacon ratio report, and a communications device poweravailability report, e.g., a communications device transmission powerbackoff report.

In various embodiments, the repetition of step 4712 following an initialcontrol information report of step 4712, e.g., while the communicationsdevice remains in the second mode of operation, includes thetransmission of a first additional control information report set,followed by a second additional control information report set, followedby another first additional control information report set, where thesecond additional control information report set includes at least onereport that is not included in the first additional control informationreport set.

As an exemplary embodiment, consider that the predetermined reportsequence is the report sequence of 40 indexed segments for the uplinkdedicated control channel segments in a beaconslot as illustrated bydrawing 1099 of FIG. 10. Further consider that the segments of thepredetermined report sequence are grouped on a superslot basis withsegment indexes (0-4), (5-9), (10-14), (15-19), (20-24), (25-29),(30-34), (35-39), and each group corresponds to a superslot of thebeaconslot. If the condition of step 4704 is satisfied, e.g., thecommunications device has just migrated from a HOLD state of operationto an ON state of operation, the communications device uses the initialreport set as indicated in Table 1199 of FIG. 11 for the firstsuperslot, and then uses the predetermined sequence of table 1099 ofFIG. 10 for subsequent superslots while remaining in the ON state. Forexample, the initial report set can replace any of the setscorresponding to segment index grouping (0-4), (5-9), (10-14), (15-19),(20-24), (25-29), (30-34, (35-39), depending upon when the statetransition to the ON mode of operation occurs.

As a variation, consider an exemplary embodiment, where there aremultiple, e.g., two, different initial control channel informationreport sets from which the communication device selects, as a functionof the position in the sequence to be replaced. FIG. 48 illustrates twoexemplary different formats of control channel information report sets4800 and 4850. Note that in the format of initial report set #1, the4^(th) segment 4810 includes a DLBNR4 report, a RSVD1 report, and anULRQST1 report, while in the format of initial report set #2, the 4^(th)segment 4860 includes a RSVD2 report and a ULRQST4 report. In anexemplary embodiment using the predetermined reporting sequence of FIG.10, if the initial control information report is to be transmitted inthe 3^(rd) superslot of a beaconslot (replacing segments indexes 10-14),then the format of initial control information report set #2 4850 isused; otherwise the format of initial control information report set #1is used. Note that in the exemplary predetermined reporting sequence ofFIG. 10, the 4 bit downlink beacon ratio report, DLBNR4, only occursonce during a beaconslot, and it occurs in the 4^(th) superslot of thebeaconslot. In this exemplary embodiment, the 2^(nd) set of formats ofinitial reports 4850 is used in the 3^(rd) superslot, since in the nextsubsequent superslot of the beaconslot (the 4^(th) superslot), thecommunications device is scheduled, in accordance with the predeterminedstructure of FIG. 10, to transmit the DLBNR4 report.

As another variation, consider an exemplary embodiment, where there aremultiple, e.g., five, different initial control channel informationreport sets from which the communications device selects, as a functionof position in the sequence to be replaced, where each of the differentinitial control information report sets is a different size. FIG. 49illustrates initial control information report set #1 4900, initialcontrol information report set #2 4910 initial control informationreport set #3 4920 initial control information report set #4 4930initial control information report set #5 4940. In an exemplaryembodiment using the predetermined reporting sequence of FIG. 10, if theinitial control information report is to be transmitted starting insegment with DCCH index value=0, 5, 10, 15, 20, 25, 30, or 35 of thebeaconslot, then initial control information report set #1 4900 is used.Alternatively, if the initial control information report is to betransmitted starting in segment with DCCH index value=1, 6, 11, 16, 21,26, 31, or 36 of the beaconslot, then initial control information reportset #2 4910 is used. Alternatively, if the initial control informationreport is to be transmitted starting in segment with DCCH index value=2,7, 12, 17, 22, 27, 32, or 37 of the beaconslot, then initial controlinformation report set #3 4920 is used. Alternatively, if the initialcontrol information report is to be transmitted starting in segment withDCCH index value=3, 8, 13, 18, 23, 28, 33, or 38 of the beaconslot, theninitial control information report set #4 4930 is used. Alternatively,if the initial control information report is to be transmitted startingin segment with DCCH index value=4, 9, 14, 19, 24, 29, 34, or 39 of thebeaconslot, then initial control information report set #5 4940 is used.

Embodiments are possible where different initial information report setsdiffer in both the size of the report set and the content of the reportset for a given DCCH segment of the superslot.

FIG. 50 is a flowchart of an exemplary method of operating a wirelessterminal in accordance with various embodiments. For example, thewireless terminal may be a mobile node in an exemplary spread spectrummultiple access orthogonal frequency division multiplexing (OFDM)wireless communications system. Operation starts in step 5002, where thewireless terminal has been powered on, established a communications linkwith a base station sector attachment point, has been allocateddedicated control channel segments to use for uplink dedicated controlchannel reports, and has been established in either a first mode ofoperation or a second mode of operation. For example, in someembodiments, the first mode of operation is a full-tone mode ofdedicated control channel operation, while the second mode of operationis a split tone mode of dedicated control channel operation. In someembodiments, each of the dedicated control channel segments includes thesame number of tone-symbols, e.g., 21 tone-symbols. Operation proceedsfrom start step 5002 to step 5004. Two exemplary types of embodimentsare illustrated in flowchart 5000. In a first type of embodiment, thebase station sends mode control signals to command changes between firstand second modes of operation. In such exemplary embodiments, operationproceeds from step 5002 to steps 5010 and 5020. In a second type ofembodiment, the wireless terminal requests mode transitions betweenfirst and second modes. In such an embodiment, operation proceeds fromstep 5002 to steps 5026 and step 5034. Embodiments are also possible,where the base station can command mode changes without input from thewireless terminal, and where the wireless terminal can request modechanges, e.g., with the base station and wireless terminal each beingcapable of initiating a mode change.

In step 5004, the WT checks as to whether the WT is currently in a firstor second mode of operation. If the WT is currently in a first mode ofoperation, e.g., a full tone mode, operation proceeds from step 5004 tostep 5006. In step 5006, the WT uses a first set of dedicated controlchannel segments during a first period of time, said first set includinga first number of dedicated control channel segments. However, if it isdetermined in step 5004, that the WT is in a second mode of operation,e.g., a split tone mode, operation proceeds from step 5004 to step 5008.In step 5008, the WT uses a second set of dedicated control channelsegments during a second period of time having the same duration of assaid first time period, said second set of control channel segmentsincluding fewer segments than said first number of segments.

For example, in one exemplary embodiment, if one considers the firstperiod of time to be a beaconslot, the first set in the full-tone modeincludes 40 DCCH segments using a single logical tone, while the secondset in the split-tone mode includes 13 DCCH segments using a singlelogical tone. The single logical tone used by the WT in the full-modemay be same or different than the single logical tone used in the splittone mode.

As another example, in the same exemplary embodiment, if one considersthe first time period to be the first 891 OFDM symbol transmission timeintervals of a beaconslot, the first set in full-tone mode includes 39DCCH segments using a single logical tone, while the second set in thesplit-tone mode includes 13 DCCH segments using a single logical tone.In this example, the first number of segments divided by the secondnumber of segments is the integer 3. The single logical tone used by theWT in the full-mode may be same or different than the single logicaltone used in the split tone mode.

During the second mode of operation, e.g., split-tone mode, the secondset of dedicated control channel segments used by the WT is, in someembodiments, a subset of a larger set of dedicated control channelsegments that can be used by the same or a different WT in a full-tonemode of operation during a time period that is not the second timeperiod. For example, the first set of dedicated control channel segmentsused during the first period of time by the wireless terminal can be thelarger set of dedicated control channel segments, and the first andsecond sets of dedicated control channel segments can correspond to thesame logical tone.

Operation proceeds from step 5002 to step 5010 for each 1^(st) type ofmode control signal directed to the WT, e.g., a mode control signalcommanding the WT to switch from a first mode to a second mode ofoperation. In step 5010, the WT receives a first type mode controlsignal from a base station. Operation proceeds from step 5010 to step5012. In step 5012 the WT checks as to whether or not it is currently ina first mode of operation. If the wireless terminal is in a first modeof operation, operation proceeds to step 5014 where the WT switches froma first mode of operation to a second mode of operation in response tosaid received control signal. However, if it is determined in step 5012that the WT is not currently in the first mode of operation, the WTproceeds via connecting node A 5016 to step 5018, where the WT stops theimplementation of the mode change since there is a misunderstandingbetween the base station and WT.

Operation proceeds from step 5002 to step 5020 for each 2^(nd) type ofmode control signal directed to the WT, e.g., a mode control signalcommanding the WT to switch from a second mode to a first mode ofoperation. In step 5020, the WT receives a second type mode controlsignal from a base station. Operation proceeds from step 5020 to step5022. In step 5022 the WT checks as to whether or not it is currently ina second mode of operation. If the wireless terminal is in a second modeof operation, operation proceeds to step 5024 where the WT switches froma second mode of operation to a first mode of operation in response tosaid received second mode control signal. However, if it is determinedin step 5022 that the WT is not currently in the second mode ofoperation, the WT proceeds via connecting node A 5016 to step 5018,where the WT stops the implementation of the mode change since there isa misunderstanding between the base station and WT.

In some embodiments, the first and/or second type of mode control changecommand signal from a base station also include information identifyingwhether the logical tone used by the WT will change following the modeswitch and, in some embodiments, information identifying the logicaltone to be used by the WT in the new mode. In some embodiments, if theWT proceeds to step 5018, the WT signals the base station, e.g.,indicating that there is a misunderstanding and that a mode transitionhas not been completed.

Operation proceeds from step 5002 to step 5026 for each time that thewireless terminal proceeds to initiate a mode change from a first modeof operation, e.g., full-tone DCCH mode, to a second mode of operation,e.g., split-tone DCCH mode. In step 5026, the WT transmits a modecontrol signal to a base station. Operation proceeds from step 5026 tostep 5028. In step 5028 the WT receives an acknowledgement signal fromthe base station. Operation proceeds from step 5028 to step 5030. Instep 5030 if the received acknowledgement signal is a positiveacknowledgment, operation proceeds to step 5032, where the wirelessterminal switches from a first mode of operation to a second mode ofoperation in response to said received positive acknowledgement signal.However, if in step 5030, the WT determines that the received signal isa negative acknowledgment signal or the WT cannot successfully decodethe received signal the WT proceeds via connecting node A 5016 to step5018 where the WT stops the mode change operation.

Operation proceeds from step 5002 to step 5034 for each time that thewireless terminal proceeds to initiate a mode change from a second modeof operation, e.g., split-tone DCCH mode, to a second mode of operation,e.g., full-tone DCCH mode. In step 5034, the WT transmits a mode controlsignal to a base station. Operation proceeds from step 5034 to step5036. In step 5036 the WT receives an acknowledgement signal from thebase station. Operation proceeds from step 5036 to step 5038. In step5038 if the received acknowledgement signal is a positiveacknowledgment, operation proceeds to step 5040, where the wirelessterminal switches from a second mode of operation to a first mode ofoperation in response to said received positive acknowledgement signal.However, if in step 5038, the WT determines that the received signal isa negative acknowledgment signal or the WT cannot successfully decodethe received signal the WT proceeds via connecting node A 5016 to step5018 where the WT stops the mode change operation.

FIG. 51 is a drawing illustrating exemplary operation in accordance withvarious embodiments. In the exemplary embodiment of FIG. 51, thededicated control channel is structured to use a repeating pattern of 16segments indexed from 0 to 15, for each logical tone in the dedicatedcontrol channel. Other embodiments may use a different number of indexedDCCH segments in a recurring pattern, e.g., 40 segments. Four exemplarylogical DCCH tones, indexed (0, 1, 2, 3) are illustrated in FIG. 51. Insome embodiments, each segment occupies the same amount of air linkresources. For example, in some embodiments, each segment has samenumber of tone-symbols, e.g., 21 tone-symbols. Drawing 5100 identifiesthe index of the segments over time for two successive iterations of thepattern corresponding to a logical tone in drawing 5104.

Drawing 5104 plots logical DCCH tone index on vertical axis 5106 vs timeon horizontal axis 5108. A first time period 5110 and a second timeperiod 5112 are shown which have the same duration. Legend 5114identifies: (i) squares with widely spaced crosshatch shading 5116represents WT1 full-tone DCCH mode segments, (ii) squares with widelyspaced vertical and horizontal line shading 5118 represent WT4 full-toneDCCH mode segments, (iii) squares with narrowly spaced vertical andhorizontal line shading 5120 represent WT5 full-tone DCCH mode segments,(iv) squares with fine crosshatch shading 5122 represent WT6 full-toneDCCH mode segments, (v) squares with widely spaced diagonal line shadingsloping upward from left to right 5124 represent WT1 split-tone DCCHmode segments, (vi) squares with narrowly spaced diagonal line shadingsloping downward from left to right 5126 represent WT2 split-tone DCCHmode segments, (vii) squares with narrowly spaced diagonal line shadingsloping upward from left to right 5128 represent WT3 split-tone DCCHmode segments, and (viii) squares with widely spaced vertical lineshading 5130 represent WT4 split-tone DCCH mode segments.

In drawing 5104, it may be observed that WT1 is in full-tone DCCH modeduring the first time period 5110 and uses a set of 15 segments (indexed0-14) corresponding to logical tone 0 during that time period. Duringthe 2^(nd) time period 5112, which is the same duration as the firsttime period, WT1 is in split-tone DCCH mode and uses a set of 5 segmentswith index values (0, 3, 6, 9, 12) corresponding to logical tone 0,which is a subset of the set of segments used during the 1^(st) timeperiod 5110.

In drawing 5104, it may also be observed that WT4 is in full-tone DCCHmode during 1^(st) time period 5110 and uses a set of 15 segments(indexed 0-14) corresponding to logical tone 2, and WT4 is in split toneformat during 2^(nd) time period 5112 and uses a set of 5 segments withindex values (1, 4, 7, 10, 13) corresponding to logical tone 3. Itshould also be observed that the set of 5 segments with index values (1,4, 7, 10, 13) corresponding to logical tone 3 is part of a larger set ofsegments used by WT6 in full-tone DCCH mode during the 1^(st) timeperiod 5110.

FIG. 52 is a flowchart 5200 of an exemplary method of operating a basestation in accordance with various embodiments. Operation of theexemplary method starts in step 5202, where the base station is poweredon and initialized. Operation proceeds to steps 5204 and steps 5206. Instep 5204, the base station, on an ongoing basis, partitions thededicated control channel resources between full-tone DCCH sub-channelsand split tone DCCH sub-channel and allocates the full-tone and splittone DCCH sub-channels among a plurality of wireless terminals. Forexample, in an exemplary embodiment the DCCH channel uses 31 logicaltones and each logical tone corresponds to 40 DCCH channel segments in asingle iteration of a repeating pattern, e.g., on a beaconslot basis. Atany given time each logical tone can correspond to either a full-toneDCCH mode of operation where DCCH segments corresponding to the tone areallocated to a single WT, or a split tone DCCH mode where DCCH segmentscorresponding to the tone can be allocated to up to a fixed maximumnumber of WTs, e.g., where the fixed maximum number of WTs=3. In such anexemplary embodiment using 31 logical tones for the DCCH channel, ifeach of the DCCH channel logical tones are in full-tone mode, the basestation sector attachment point can have allocated DCCH segments to 31WTs. At the other extreme if each of the DCCH channel logical tones arein split-tone format, then 93 WTs can be assigned segments. In general,at any given time the DCCH channel is partitioned and may include amixture of full and split tone sub-channels, e.g., to accommodatecurrent loading conditions and current needs of the WTs using the basestation as their attachment point.

FIG. 53 illustrates exemplary partitioning and allocation of dedicatedcontrol channel resources for another exemplary embodiment, e.g., anembodiment using 16 indexed DCCH segments corresponding to a logicaltone which repeat on a recurring basis. The method described withrespect to FIG. 53 may be used in step 5204 and may be extended to otherembodiments.

Step 5204 includes sub-step 5216, in which the base station communicatesto the WTs sub-channel allocation information. Sub-step 5216 includessub-step 5218. In sub-step 5218, the base station assigns useridentifiers to WTs receiving allocation of dedicated control channelsegments, e.g., on state user identifiers.

In step 5206, the base station, on an ongoing basis, receives uplinksignals from WTs including dedicated control channel reportscommunicated on the allocated DCCH sub-channels. In some embodiments,the wireless terminals use different coding to communicate informationtransmitted in DCCH segments during a full-tone DCCH mode of operationand during a split-tone DCCH mode of operation; therefore the basestation performs different decoding operations based on the mode.

Two exemplary types of embodiments are illustrated in flowchart 5200. Ina first type of embodiment, the base station sends mode control signalsto command changes between first and second modes of operation, e.g.,between full-tone DCCH mode and split-tone DCCH mode. In such exemplaryembodiments, operation proceeds from step 5202 to steps 5208 and 5010.In a second type of embodiment, the wireless terminal requests modetransitions between first and second modes, e.g., between full-tone DCCHmode and split-tone DCCH mode. In such an embodiment, operation proceedsfrom step 5202 to steps 5212 and step 5214. Embodiments are alsopossible where the base station can command mode changes without inputfrom the wireless terminal, and where the wireless terminal can requestmode changes, e.g., with the base station and wireless terminal eachbeing capable of initiating a mode change.

Operation proceeds to step 5208 for each instance where the base stationdecides to command a WT to change from a first mode, e.g., full-modeDCCH mode to a second mode, e.g. split-tone DCCH mode. In step 5208, thebase station sends a mode control signal to a WT to initiate a WTtransition from a first mode, e.g., full-tone DCCH mode, to a secondmode, e.g., split-tone DCCH mode.

Operation proceeds to step 5210 for each instance where the base stationdecides to command a WT to change from the second mode, e.g., split-modeDCCH mode, to the first mode, e.g. full-tone DCCH mode. In step 5210,the base station sends a mode control signal to a WT to initiate a WTtransition from the second mode, e.g., split-tone DCCH mode, to thefirst mode, e.g., full-tone DCCH mode.

Operation proceeds to step 5212 for each instance where the base stationreceives a request from a WT to change from a first mode, e.g.,full-tone DCCH mode to a second mode, e.g. split-tone DCCH mode. In step5212, the base station receives a mode control signal from a WTrequesting a transition from a first mode of operation to a second modeof operation, e.g., from full-tone DCCH mode to split-tone DCCH mode.Operation proceeds from step 5212 to step 5220, if the base stationdecides to accommodate the request. In step 5220, the base stationtransmits a positive acknowledgement signal to the WT which sent therequest.

Operation proceeds to step 5214 for each instance where the base stationreceives a request from a WT to change from a second mode, e.g.,split-tone DCCH mode to a first mode, e.g. full-tone DCCH mode. In step5214, the base station receives a mode control signal from a WTrequesting a transition from a second mode of operation to a first modeof operation, e.g., from split-tone DCCH mode to full-tone DCCH mode.Operation proceeds from step 5214 to step 5222, if the base stationdecides to accommodate the request. In step 5222, the base stationtransmits a positive acknowledgement signal to the WT which sent therequest.

FIG. 53 is a drawing illustrating exemplary operation in accordance withvarious embodiments. In the exemplary embodiment of FIG. 53, thededicated control channel is structured to use a repeating pattern of 16segments indexed from 0 to 15, for each logical tone in the dedicatedcontrol channel. Other embodiments may use a different number of indexedDCCH segments in a recurring pattern, e.g., 40 segments. Three exemplarylogical DCCH tones, indexed (0, 1, 2) are illustrated in FIG. 53. Insome embodiments, each segment occupies the same amount of air linkresources. For example, in some embodiments, each segment has samenumber of tone-symbols, e.g., 21 tone-symbols. Drawing 5300 identifiesthe index of the segments over time for two successive iterations of therecurring indexing pattern corresponding to a logical tone in drawing5304.

Drawing 5304 plots logical DCCH tone index on vertical axis 5306 vs timeon horizontal axis 5308. A first time period 5310 and a second timeperiod 5312 are shown which have the same duration. Legend 5314identifies: (i) squares with widely spaced crosshatch shading 5316represents WT1 full-tone DCCH mode segments, (ii) squares with narrowlyspaced crosshatch shading 5318 represents WT2 full-tone DCCH modesegments, (iii) squares with widely spaced vertical and horizontal lineshading 5320 represent WT4 full-tone DCCH mode segments, (iv) squareswith narrowly spaced vertical and horizontal line shading 5322 representWT9 full-tone DCCH mode segments, (v) squares with widely spaceddiagonal line shading sloping upward from left to right 5324 representWT1 split-tone DCCH mode segments (vi) squares with narrowly spaceddiagonal line shading sloping downward from left to right 5326 representWT2 split-tone DCCH mode segments, (vii) squares with narrowly spaceddiagonal line shading sloping upward from left to right 5328 representWT3 split-tone DCCH mode segments, (viii) squares with widely spacedvertical line shading 5330 represent WT4 split-tone DCCH mode segments,and (ix) squares with narrowly spaced vertical line shading 5332represent WT5 split-tone DCCH mode segments, (x) squares with widelyspaced horizontal line shading 5334 represent WT6 split-tone DCCH modesegments, (xi) squares with narrowly spaced horizontal line shading 5336represent WT7 split-tone DCCH mode segments, and (xii) squares with dotshading 5338 represent WT8 split-tone DCCH mode segments.

In drawing 5304, it may be observed that WT1 is in full-tone DCCH modeduring the first time period 5310 and uses a set of 15 segments (indexed0-14) corresponding to logical tone 0 during that time period. Inaccordance with some embodiments, a base station allocated a firstdedicated control sub-channel to WT1, the first dedicated controlsub-channel including the set of 15 segments (indexed 0-14)corresponding to logical tone 0 for use during 1^(st) time period 5310.

In drawing 5304, it may also be observed that WT2, WT3, and WT4 are eachsplit-tone DCCH mode during the first time period 5310 and each use aset of 5 segments indexed ((0, 3, 6, 9, 12), (1, 4, 7, 10, 13), (2, 5,8, 11, 14)), respectively corresponding to the same logical tone,logical tone 1 during 1st time period 5310. In accordance with someembodiments, a base station allocated a (second, third, and fourth)dedicated control sub-channel to (WT2, WT3, WT3), the (second, third,and fourth) dedicated control sub-channels each including a set of 5segments with index values ((0, 3, 6, 9, 12), (1, 4, 7, 10, 13), (2, 5,8, 11, 14)), respectively corresponding to the same logical tone,logical tone 1 during 1st time period 5310.

In drawing 5304, it may also be observed that WT6, WT7, and WT8 are eachsplit-tone DCCH mode during the first time period 5310 and each use aset of 5 segments indexed ((0, 3, 6, 9, 12), (1, 4, 7, 10, 13), (2, 5,8, 11, 14)), respectively corresponding to the same logical tone,logical tone 2 during 1st time period 5310. In accordance with someembodiments, a base station allocated a (fifth, sixth, and seventh)dedicated control sub-channel to (WT6, WT7, WT8), the (fifth, sixth, andseventh) dedicated control sub-channels each including a set of 5segments with index values ((0, 3, 6, 9, 12), (1, 4, 7, 10, 13), (2, 5,8, 11, 14)), respectively corresponding to the same logical tone,logical tone 2 during 1st time period 5310.

In drawing 5304, it may be observed that (WT1, WT5) are in split-toneDCCH mode during the second time period 5312 and each uses a set of 5segments with index values (0, 3, 6, 9, 12), (1, 4, 7, 10, 13)),respectively, corresponding to logical tone 0 during the second timeperiod 5312. In accordance with various embodiments, a base stationallocated an (eighth, ninth) dedicated control sub-channel to (WT1,WT5), the (eighth, ninth) dedicated control sub-channel including theset of 5 segments with index (0, 3, 6, 9, 12), (1, 4, 7, 10, 13)),respectively, corresponding to logical tone 0 during the second timeperiod 5312. WT1 used logical tone 0 during the first time period, whileWT 5 did not use logical tone 0 during the first time period.

In drawing 5304, it may also be observed that (WT2) is in full-tone DCCHmode during the second time period 5312 and uses a set of 15 segmentsindexed (0-14) corresponding to logical tone 1 during the second timeperiod 5312. In accordance with some embodiments, a base stationallocated a (tenth) dedicated control sub-channel to (WT2), thededicated control sub-channel including the set of 15 segments indexed(0-14) corresponding to logical tone 1 during the second time period5312. It may be noted that WT2 is one of the WTs from the set of (WT2,WT3, WT4) which used logical tone 1 during the first time period 5310.

In drawing 5304, it may also be observed that (WT9) is in full-tone DCCHmode during the second time period 5312 and each uses a set of 15segments indexed (0-14) corresponding to logical tone 2 during thesecond time period 5312. In accordance with some embodiments, a basestation allocated an (eleventh) dedicated control sub-channel to (WT9),the dedicated control sub-channel including the set of 15 segmentsindexed (0-14) corresponding to logical tone 2 during the second timeperiod 5312. It may be noted that WT9 is a different WT than the WTs(WT6, WT7, WT8) which used logical tone 2 during the first time period5310.

In some embodiments, the logical tones (tone 0, tone 1, tone 2) aresubjected to an uplink tone hopping operation which determines whichphysical tones the logical tones correspond to for each of a pluralityof symbol transmission time periods, e.g., in the first time period5310. For example, logical tones 0, 1, and 2 may be part of a logicalchannel structure including 113 logical tones, which are hopped, inaccordance with a hopping sequence to a set of 113 physical tones usedfor uplink signaling. Continuing with the example, consider that eachDCCH segment corresponds to a single logical tone and corresponds to 21successive OFDM symbol transmission time intervals. In an exemplaryembodiment, the logical tone is hopped such that the logical tonecorresponding to three physical tones, with the wireless terminal usingeach physical tone for seven consecutive symbol transmission timeintervals of the segment.

In an exemplary embodiment using 40 indexed DCCH channel segmentscorresponding to a logical tone which repeat on a recurring basis, anexemplary 1^(st) and 2^(nd) time period may each include 39 DCCHsegments, e.g., the first 39 DCCH segments of a beaconslot correspondingto the logical tone. In such an embodiment, if a given tone is infull-tone format, a WT is allocated by the base station a set of 39 DCCHsegments for the 1^(st) or 2^(nd) time period corresponding to theallocation. If a given tone is in split-tone format, a WT is allocated aset of 13 DCCH segments for the 1^(st) or 2^(nd) time periodcorresponding to the allocation. In full-tone mode the 40^(th) indexedsegment can also be allocated to and used by the WT in full-tone mode.In split-tone mode, in some embodiments, the 40^(th) indexed segment isa reserved segment.

FIG. 54 is a drawing of a flowchart 5400 of an exemplary method ofoperating a wireless terminal in accordance with various embodiments.Operation starts in step 5402 where the wireless terminal is powered onand initialized. Operation proceeds from step 5402 to steps 5404, 5406,and 5408. In step 5404, the wireless terminal measures the receivedpower of a downlink null channel (DL.NCH) and determines an interferencepower (N). For example, the Null channel corresponds to predeterminedtone-symbols in an exemplary downlink timing and frequency structureused by the base station serving as the current attachment point for thewireless terminal in which the base station intentionally does nottransmit using those tone-symbols; therefore, received power on the NULLchannel measured by the wireless terminal receiver representsinterference. In step 5406, the wireless terminal measures the receivedpower (G*P₀) of a downlink pilot channel (DL.PICH). In step 5408, thewireless terminal measures the signal to noise ratio (SNR₀) of thedownlink pilot channel (DL.PICH). Operation proceeds from steps 5404,5406, and 5408 to step 5410.

In step 5410, the wireless terminal calculates the saturation level ofthe downlink signal to noise ratio as a function of: the interferencepower, measured received power of the downlink pilot channel, andmeasured SNR of the downlink pilot channel. For example, saturationlevel of the DL SNR=1/a₀=(1/SNR₀−N/(GP₀))⁻¹. Operation proceeds fromstep 5410 to steps 5412. In step 5412, the wireless terminal selects thecloset value from a predetermined table of quantized level of saturationlevel of downlink SNR to represent the calculated saturation level in adedicated control channel report, and the wireless terminal generatesthe report. Operation proceeds from step 5412 to step 5414. In step5414, the wireless terminal transmits the generated report to the basestation, said generated report being communicated using a dedicatedcontrol channel segment allocated to the wireless terminal, e.g., usinga predetermined portion of a predetermined indexed dedicated controlchannel segment. For example, the exemplary WT may be in a full-toneformat mode of DCCH operation using the repetitive reporting structureof FIG. 10, and the report may be the DLSSNR4 reports of DCCH segment1036 with index numbers s2=36.

FIG. 55 is a drawing of an exemplary wireless terminal 5500, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary WT 5500 may be any of the wireless terminals of the exemplarysystem of FIG. 1. Exemplary wireless terminal 5500 includes a receivermodule 5502, a transmitter module 5504, a processor 5506, user I/Odevices 5508, and a memory 5510 coupled together via a bus 5512 overwhich the wireless terminal 5500 interchanges data and information.

The receiver module 5502, e.g., an OFDM receiver, is coupled to areceive antenna 5503 via which the wireless terminal 5500 receivesdownlink signals from base stations. Downlink signals received by thewireless terminal 5500 include: mode control signals, mode controlrequest response signals, assignment signals including the assignment ofuser identifiers, e.g., an ON identifier associated with a logicaluplink dedicated control channel tone, uplink and/or downlink trafficchannel assignment signals, downlink traffic channel signals, anddownlink base station identification signals. Receiver module 5502includes a decoder 5518 via which the wireless terminal 5500 decodesreceived signals which had been encoded prior to transmission by thebase station. The transmitter module 5504, e.g., an OFDM transmitter, iscoupled to a transmit antenna 5505 via which the wireless terminal 5500transmits uplink signals to base stations. In some embodiments, the sameantenna is used for transmitter and receiver. Uplink signals transmittedby the wireless terminal include: mode request signals, access signals,dedicated control channel segment signals during first and second modesof operation, and uplink traffic channel signals. Transmitter module5504 includes an encoder 5520 via which the wireless terminal 5500encodes at least some uplink signals prior to transmission. Encoder 5520includes a 1^(st) coding module 5522 and a 2^(nd) coding module 5524.1^(st) coding module 5522 codes information to be transmitted in DCCHsegments during the first mode of operation according to a first codingmethod. 2^(nd) coding module 5524 codes information to be transmitted inDCCH segments during the second mode of operation according to a secondcoding method; the first and second coding methods are different.

User I/O devices 5508, e.g., microphone, keyboard, keypad, mouse,switches, camera, display, speaker, etc., are used to inputdata/information, output data/information, and control at least somefunctions of the wireless terminal, e.g., initiate a communicationssession. Memory 5510 includes routines 5526 and data/information 5528.The processor 5506, e.g., a CPU, executes the routines 5526 and uses thedata/information 5528 in memory 5510 to control the operation of thewireless terminal 5500 and implement methods.

Routines 5526 include a communications routine 5530 and wirelessterminal control routines 5532. The communications routine 5530implements the various communications protocols used by the wirelessterminal 5500. The wireless terminal control routines 5532 controloperation of the wireless terminal 5500 including controlling operationof the receiver module 5502, transmitter module 5504 and user I/Odevices 5508. Wireless terminal control routines 5532 include a firstmode dedicated control channel communications module 5534, a second modededicated control channel communications module 5536, a dedicatedcontrol channel mode control module 5538, a mode request signalgeneration module 5540, a response detection module 5542, and an uplinkdedicated control channel tone determination module 5543.

The first mode dedicated control channel communications module 5534controls dedicated control channel communications using a first set ofdedicated control channel segments during a first mode of operation,said first set including a first number of control channel segments fora first period of time. The first mode is, in some embodiments, a fulltone mode, of dedicated control channel operation. The second modededicated control channel communications module 5536 controls dedicatedcontrol channel communications using a second set of dedicated controlchannel segments during a second mode of operation, said second set ofdedicated control channel segments corresponding to a time period havingthe same duration as said first period of time, said second set ofdedicated control channel segments including fewer segments than saidfirst number of dedicated control channel segments. The second mode is,in some embodiments, a split-tone mode, of dedicated control channeloperation. In various embodiments, a dedicated control channel segmentwhether in the first mode or the second mode of operation uses the sameamount of uplink air link resources, e.g., the same number oftone-symbols, e.g., 21 tone-symbols. For example, a dedicated controlchannel segment may correspond to one logical tone in the timing andfrequency structure being used by the base station, but may correspondto three physical tones with three sets of seven tone-symbols each beingassociated with a different physical uplink tone in accordance withuplink tone hopping information.

DCCH mode control module 5538, in some embodiments, controls switchinginto one said first mode of operation and said second mode of operationin response to a received mode control signal from a base station, e.g.,a mode control command signal from a base station. In some embodiments,the mode control signal also identifies, for the split tone mode ofoperation, which set of uplink dedicated control channel segments isassociated with the split tone mode of operation. For example, for agiven logical DCCH channel tone, in split tone operation, there may be aplurality, e.g., three, non-overlapping sets of DCCH segments and themode control signal may identify which of the sets is to be associatedwith the wireless terminal. DCCH mode control module 5538, in someembodiments, controls switching into a requested mode of operation whichis one of the first mode of operation, e.g., full-tone DCCH mode, andthe second mode of operation, e.g., split-tone DCCH mode, in response toa received affirmative request acknowledgment signal.

Mode request generation module 5540 generates a mode request signalindicating a requested mode of DCCH operation. Response detection module5542 detects a response to said mode request signal from the basestation. The output of response detection module 5542 is used by theDCCH mode control module 5538 to determine if the wireless terminal 5500is to be switched into the requested mode of operation.

Uplink DCCH tone determination module 5543 determines the physical toneto which an assigned logical DCCH tone corresponds to over time based onthe uplink tone hopping information stored in the wireless terminal.

Data/information 5528 includes user/device/session/resource information5544, system data/information 5546, current mode of operationinformation 5548, terminal ID information 5550, DCCH logical toneinformation 5552, mode request signal information 5554, timinginformation 5556, base station identification information 5558, data5560, DCCH segment signal information 5562, and mode request responsesignal information 5564. User/device/session/resource information 5544includes information corresponding to peer nodes in communicationssessions with WT 5500, address information, routing information, sessioninformation including authentication information, and resourceinformation including allocated DCCH segments and uplink and/or downlinktraffic channel segments associated with the communications sessionwhich are allocated to WT 5500. Current mode of operation information5548 includes information identifying whether the wireless terminal iscurrently in a first, e.g., full-tone DCCH mode of operation, or asecond, e.g., split-tone DCCH mode of operation. In some embodiments,the first and second modes of operation with respect to the DCCH bothcorrespond to wireless terminal On states of operation. Current mode ofoperation information 5548 also includes information identifying othermodes of wireless terminal operation, e.g., sleep, hold, etc. Terminalidentifier information 5550 includes base station assigned wirelessterminal identifiers, e.g., registered user identifier and/or an ONstate identifier. In some embodiments, the ON state identifier isassociated with a DCCH logical tone being used by the base stationsector attachment point which allocated the On state identifier to thewireless terminal. DCCH logical tone information 5552 includes, when thewireless terminal is in one of first mode of DCCH operation and a secondmode of DCCH operation, information identifying the DCCH logical tonecurrently allocated to the wireless terminal to use when communicatinguplink DCCH segment signals. Timing information 5556 includesinformation identifying the wireless terminals current timing within therepetitive timing structure being used by the base stations serving asan attachment point for the wireless terminal. Base stationidentification information 5558 includes base station identifiers, basestation sector identifiers, and base station tone block and/or carrieridentifiers associated with the base station sector attachment pointbeing used by the wireless terminal. Data 5560 includes uplink and/ordownlink user data being communicated in communications sessions, e.g.,voice, audio data, image data, text data, file data. DCCH segment signalinformation 5562 includes information to be communicated correspondingto DCCH segments allocated to the wireless terminal, e.g., informationbits to be communicated in DCCH segments representing various controlinformation reports. Mode request signal information 5554 includesinformation corresponding to mode request signals generated by module5540. Mode request response signal information 5564 includes responseinformation detected by module 5542.

System data/information 5546 includes full tone mode DCCH information5566, split-tone mode DCCH information 5568, and a plurality of sets ofbase station data/information (base station 1 data/information 5570, . .. , base station M data/information 5572). Full tone mode DCCHinformation 5566 includes channel structure information 5574 and segmentcoding information 5576. Full tone mode DCCH channel structureinformation 5574 includes information identifying segments and reportsto be communicated in segments when the wireless terminal is in afull-tone DCCH mode of operation. For example, in one exemplaryembodiment, there is a plurality of DCCH tones, e.g., 31 in the DCCHchannel, each logical DCCH tone when in the full-tone mode, following arecurring pattern of forty DCCH segments associated with the singlelogical DCCH tone in the DCCH channel. Full tone mode DCCH segmentcoding information 5576 includes information used by 1^(st) codingmodule 5522 to encode DCCH segments. Split-tone mode DCCH information5568 includes channel structure information 5578 and segment codinginformation 5580. Split-tone mode DCCH channel structure information5578 includes information identifying segments and reports to becommunicated in segments when the wireless terminal is in a split-toneDCCH mode of operation. For example, in one exemplary embodiment, thereis a plurality of DCCH tones, e.g., 31 in the DCCH channel, each logicalDCCH tone when in the split-tone mode is split over time among up tothree different WTs. For example, for a given logical DCCH tone a WTreceives a set of 13 DCCH segments to use out of 40 segments in arecurring pattern, each set of 13 DCCH segments being non-overlappingwith the other two sets of 13 DCCH segments. In such an embodiment, onemay consider, e.g., a time interval in the structure including 39 DCCHsegments allocated to a single WT if in the full-tone mode, butpartitioned among three wireless terminals in the split-tone format.Split-tone mode DCCH segment coding information 5580 includesinformation used by 2^(nd) coding module 5524 to encode DCCH segments.

In some embodiments, during one time period a given logical DCCH tone isused in a full-tone mode of operation, while at other times the samelogical DCCH tone is used in a split tone mode of operation. Thus WT5500 can be allocated a set of DCCH channel segments in a recurringstructure while in the split-tone mode of DCCH operation which is asubset of a larger set of DCCH channel segments used in the full-tonemode of operation.

Base station 1 data/information 5570 includes base stationidentification information used to identify base station, sector,carrier and/or tone block associated with an attachment point. Basestation 1 data/information 5570 also includes downlink timing/frequencystructure information 5582 and uplink timing/frequency structureinformation 5584. Uplink timing/frequency structure information 5584includes uplink tone hopping information 5586.

FIG. 56 is a drawing of an exemplary base station 5600, e.g., accessnode, implemented in accordance with various embodiments. Exemplary basestation 5600 may be any of the base stations of the exemplary system ofFIG. 1. Exemplary base station 5600 includes a receiver module 5602, atransmitter module 5604, a processor 5608, an I/O interface 5610, and amemory 5612 coupled together via a bus 5614 over which the variouselements interchange data and information.

Receiver module 5602, e.g., an OFDM receiver, receives uplink signalsfrom a plurality of wireless terminals via receive antenna 5603. Theuplink signals include dedicated control channel segment signals fromwireless terminals, requests for mode changes, and uplink trafficchannel segment signals. Receiver module 5602 includes a decoder module5615 for decoding uplink signals which were encoded prior totransmission by the wireless terminals. The decoder module 5615 includesa first decoder sub-module 5616 and a second decoder sub-module 5618.The first decoder sub-module 5616 decodes information received indedicated control channel segments corresponding to logical tones usedin a full-tone DCCH mode of operation. The second decoder sub-module5618 decodes information received in dedicated control channel segmentscorresponding to logical tones used in a split-tone DCCH mode ofoperation; the first and second decoder sub-modules (5616, 5618)implement different decoding methods.

Transmitter module 5604, e.g., an OFDM transmitter, transmits downlinksignals to wireless terminals via transmit antenna 5605. Transmitteddownlink signals include registration signals, DCCH control signals,traffic channel assignment signals, and downlink traffic channelsignals.

I/O interface 5610 provides an interface for coupling the base station5600 to other network nodes, e.g., other base stations, AAA servernodes, home agent nodes, routers, etc., and/or the Internet. I/Ointerface 5610 allows a wireless terminal using base station 5600 as itspoint of network attachment to communicate with peer nodes, e.g., otherwireless terminals, in different cells, via a backhaul communicationnetwork.

Memory 5612 includes routines 5620 and data/information 5622. Theprocessor 5608, e.g. a CPU, executes the routines 5620 and uses thedata/information 5622 in memory 5612 to control the operation of thebase station 5600 and implement methods. Routines 5620 include acommunications routines 5624, and base station control routines 5626.The communications routines 5624 implement the various communicationsprotocols used by the base station 5600. Base station control routines5626 include a control channel resource allocation module 5628, alogical tone dedication module 5630, a wireless terminal dedicatedcontrol channel mode control module 5632, and a scheduler module 5634.

The control channel resource allocation module 5628 allocates dedicatedcontrol channel resources including logical tones corresponding todedicated control channel segments in an uplink. The control channelresource allocation module 5628 includes a full tone allocationsub-module 5636 and a split-tone allocation sub-module 5638. The fulltone allocation sub-module 5636 allocates one of said logical tonescorresponding to the dedicated control channel to a single wirelessterminal. The split-tone allocation sub-module 5638 allocates differentsets of dedicated control channel segments corresponding to one of thelogical tones corresponding to the dedicated control channel to aplurality of wireless terminals to be used on a time shared basis witheach of the plurality of wireless terminal being dedicated a differentnon-overlapping portion of time in which said logical tone is to be usedon a time shared basis. For example, in some embodiments, a singlelogical dedicated control channel tone may be allocated to and shared byup three wireless terminals in the split-tone mode of operation. At anygiven time full tone allocation sub-module 5636 may be operating onnone, some, or each of the DCCH channel tones; at any given time thesplit-tone allocation sub-module 5638 may be operating on none, some, oreach of the DCCH channel tones.

The logical tone dedication module 5630 controls whether a logicaldedicated control channel tone is to be used to implement a full tonededicated control channel or a split-tone dedicated control channel. Thelogical tone dedication module 5630 is responsive to wireless terminalloading to adjust the number of logical tones dedicated to full-tonededicated control channels and to split-tone dedicated control channels.In some embodiments, the logical tone dedication module 5630 isresponsive to requests from a wireless terminal to operate in either afull-tone mode or a split-tone mode and adjusts the allocation oflogical tones as a function of received wireless terminal requests. Forexample, base station 5600, in some embodiments, for a given sector anduplink tone block uses a set of logical tones for the dedicated controlchannels, e.g., 31 logical tones, and at any given time the logicaldedicated control channel tones are partitioned among full-tone modelogical tones and split-tone mode logical tones by logical tonededication module 5630.

Wireless terminal dedicated control channel mode control module 5632generates control signals for indicating logical tone assignments anddedicated control channel mode assignments to wireless terminals. Insome embodiments, a wireless terminal is assigned an ON state identifierby the generated control signals, and the value of the ON identifier isassociated with a particular logical dedicated control channel tone inthe uplink channel structure. In some embodiments, the assignmentsgenerated by module 5632 indicate that a wireless terminal correspondingto an assignment should operate in a full tone or split-tone mode withrespect to an assigned logical tone. The split tone mode assignmentsfurther indicate which of a plurality of segments corresponding to anassigned logical dedicated control channel tone the wireless terminalcorresponding to the assignment should use.

Scheduler module 5634 schedules uplink and/or downlink traffic channelsegments to wireless terminals, e.g., to wireless terminals which areusing the base station 5600 as their point of network attachment, are inan On state and currently have an assigned dedicated control channeleither in split-tone mode or full-tone mode.

Data/information 5622 includes system data/information 5640, currentDCCH logical tone implementation information 5642, received DCCH signalinformation 5644, DCCH control signal information 5646, and a pluralityof sets of wireless terminal data/information 5648 (WT 1data/information 5650, . . . , WT N data/information 5652). Systemdata/information 5640 includes full tone mode DCCH information 5654,split-tone mode DCCH information 5656, downlink timing/frequencystructure information 5658 and uplink timing/frequency structureinformation 5660. Full-tone mode DCCH information 5654 includesfull-tone mode channel structure information 5662 and full tone modesegment coding information 5664. Split-tone mode DCCH information 5656includes split-tone mode channel structure information 5666 andsplit-tone mode segment coding information 5668. Uplink timing/frequencystructure information 5660 includes uplink tone hopping information5660. Each single logical tone in an uplink tone block channel structurecorresponds to a physical tone which is hopped in frequency over time.For example consider a single logical dedicated control channel tone. Insome embodiments, each DCCH segment corresponding to the single logicalDCCH tone comprises 21 OFDM tone-symbols corresponding to a firstphysical tone used for seven consecutive OFDM symbol time periods, asecond physical tone used for seven consecutive OFDM symbol timeperiods, and a third physical tone used for seven consecutive OFDMsymbol time periods, the first, second, and third tones being selectedin accordance with an implemented uplink tone-hopping sequence known toboth the base station and wireless terminal. For at least some of thededicated control channel logical tones for at least some DCCH segments,the first, second and third physical tones are different.

Current DCCH logical tone implementation information 5642 includesinformation identifying the decisions of logical tone dedication module5630, e.g., whether each given logical dedicated control channel tone iscurrently being used in full-tone format or split-tone format. ReceivedDCCH signal information 5644 includes information received on any of thededicated control channel segments in the uplink dedicated controlchannel structure of the base station 5600. DCCH control signalinformation 5646 includes assignment information corresponding toassigning dedicated control channel logical tones and modes of dedicatedcontrol channel operation. DCCH control signal information 5646 alsoincludes received requests from a wireless terminal for a dedicatedcontrol channel, requests for a DCCH mode of operation, and/or requestsfor a change of DCCH mode of operation. DCCH control signal information5646 also includes acknowledgment signaling information in response toreceived requests from wireless terminals.

WT 1 data/information 5650 includes identification information 5662,received DCCH information 5664, and user data 5666. Identificationinformation 5662 includes a base station assigned WT On identifier 5668and mode information 5670. In some embodiments, the base stationassigned On identifier value is associated with a logical dedicatedcontrol channel tone in the uplink channel structure used by the basestation. Mode information 5650 includes information identifying whetherthe WT is in a full-tone DCCH mode of operation or a split-tone modeDCCH mode of operation, and when the WT is in a split tone-modeinformation associating the WT with a subset of DCCH segments associatedwith the logical tone. Received DCCH information 5664 includes receivedDCCH reports associated with WT1, e.g., conveying uplink traffic channelrequests, beacon ratio reports, power reports, self-noise reports,and/or signal to noise ratio reports. User data 5666 includes uplinkand/or downlink traffic channel user data associated with WT1, e.g.,voice data, audio data, image data, text data, file data, etc.,corresponding to communications sessions and communicated via uplinkand/or downlink traffic channel segments allocated to the WT1.

FIG. 57 is a drawing of an exemplary wireless terminal 5700, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary WT 5700 may be any of the wireless terminals of the exemplarysystem of FIG. 1. Exemplary wireless terminal 5700 includes a receivermodule 5702, a transmitter module 5704, a processor 5706, user I/Odevices 5708, and a memory 5710 coupled together via a bus 5712 overwhich the wireless terminal interchanges data and information.

The receiver module 5702, e.g., an OFDM receiver, is coupled to areceive antenna 5703 via which the wireless terminal 5700 receivesdownlink signals from base stations. Downlink signals received by thewireless terminal 5700 include beacon signals, pilot signals,registration response signals, power control signals, timing controlsignals, assignments of wireless terminal identifiers, e.g., an On stateidentifier corresponding to a DCCH channel logical tone, other DCCHassignment information, e.g., used to identify a set of DCCH channelsegments in a uplink repetitive structure, assignments of uplink trafficchannel segments and/or assignment of downlink traffic channel segments.Receiver module 5702 includes a decoder 5714 via which the wirelessterminal 5700 decodes received signals which had been encoded prior totransmission by the base station. The transmitter module 5704, e.g., anOFDM transmitter, is coupled to a transmit antenna 5705 via which thewireless terminal 5700 transmits uplink signals to base stations. Uplinksignals transmitted by the wireless terminal 5700 include: accesssignals, handoff signals, power control signals, timing control signals,DCCH channel segment signals, and uplink traffic channel segmentsignals. DCCH channel segment signals include initial DCCH report setsignals and scheduled DCCH report set signals. In some embodiments, thesame antenna is used for transmitter and receiver. Transmitter module5704 includes an encoder 5716 via which the wireless terminal 5700encodes at least some uplink signals prior to transmission.

User I/O devices 5708, e.g., microphone, keyboard, keypad, mouse,switches, camera, display, speaker, etc., are used to inputdata/information, output data/information, and control at least somefunctions of the wireless terminal, e.g., initiate a communicationssession. Memory 5710 includes routines 5718 and data/information 5720.The processor 5706, e.g., a CPU, executes the routines 5718 and uses thedata/information 5720 in memory 5710 to control the operation of thewireless terminal 5700 and implement methods.

Routines 5718 include a communications routine 5722 and wirelessterminal control routines 5724. The communications routine 5722implements the various communications protocols used by the wirelessterminal 5700. The wireless terminal control routines 5724 controloperation of the wireless terminal 5700 including controlling operationof the receiver module 5702, transmitter module 5704 and user I/Odevices 5708. Wireless terminal control routines 5724 include a reporttransmission control module 5726, an initial report generation module5728, a scheduled report generation module 5730, and a timing controlmodule 5732. The report transmission control module 5726 includes ahandoff detection module 5734. The initial report generation module 5728includes a report size set determination sub-module 5736.

Report transmission control module controls the wireless terminal 5700to transmit an initial information report set following the transitionby said wireless terminal from a first mode of operation to a secondmode of operation and to transmit scheduled reports according to anuplink reporting schedule following transmission of said initial reportset. In some embodiments the first mode of operation is one of a sleepstate and a hold state and the second mode of operation is an ON state,e.g., an On state in which the wireless terminal is permitted totransmit user data. In various embodiments, in the second mode, e.g., ONstate, the wireless terminal has a dedicated uplink reporting channelfor reporting information including requests for uplink traffic channelresources which can be used to transmit user data. In variousembodiments, in the first mode, e.g., sleep state or Hold state, thewireless terminal does not have a dedicated uplink reporting channel forreporting information including requests for uplink traffic channelresources which can be used to transmit user data.

The initial report generation module 5728, which is responsive to thereport transmission control module 5726, generates an initialinformation report set as a function of a point in time with respect toan uplink transmission schedule at which said initial report set is tobe transmitted. Scheduled report generation module 5730 generatesscheduled report information sets to be transmitted following saidinitial information report. The timing control module 5732 correlatesthe uplink reporting structure based on downlink signals received fromthe base station, e.g., as part of closed loop timing control. In someembodiments, the timing control module 5732 is implemented, eitherpartially or entirely as a timing control circuit. The handoff detectionmodule 5734 detects a handoff from a first access node attachment pointto a second access node attachment point and controls the wirelessterminal to generate an initial information report set following certaintypes of identified handoffs, the generated initial information reportset to be transmitted to the second access node attachment point. Thecertain types of identified handoffs include, in some embodiments,handoffs in which the wireless terminal transitions though an accessstate of operation with respect to the second access node attachmentpoint before going to an On state with respect to the second accessnode. For example, the first and access node attachment points maycorrespond to different access nodes located in different cells whichare not timing synchronized with respect to one another and the wirelessterminal needs to go through the access state to achieve timingsynchronization with respect to the second access node.

The handoff detection module 5734 controls the wireless terminal toforgo the generation and transmission of an initial information reportfollowing a handoff from a first access node attachment point to asecond access node attachment point, under certain other types ofhandoffs, and to proceed directly into transmitting scheduled reportinformation sets. For example, the first and second access nodeattachment points may be timing synchronized and correspond to the sameaccess node, e.g., different adjacent sectors and/or tone blocks, andthe certain other type of handoff is, e.g., a handoff which involves atransition from an ON state with respect to the first attachment pointto an On state with respect to the second attachment point withouthaving to transition through an access state.

Report set size determination sub-module 5736 determines an initialreport set size as a function of the point in time with respect to theuplink transmission schedule at which said initial report is to betransmitted. For example, an initial report information set size is, insome embodiments, one of a plurality of set sizes, e.g., correspondingto one, two three, four or five DCCH segments, depending upon where inthe uplink timing structure the initial report transmission is to bestarted, e.g., the point within a superslot. In some embodiments, thetypes of reports included in the initial report set is a function ofwhere in the uplink timing structure the initial report transmission isto be started, e.g., depending upon the superslot location within abeaconslot.

Data/information 5720 includes user/device/session/resource information5738, system data/information 5740, base station identificationinformation 5742, terminal identification information 5744, timingcontrol information 5746, current state of operation information 5748,DCCH channel information 5750, initial report time information 5752,determined initial report size information 5754, initial report controlinformation 5756, generated initial report information set 5758,generated scheduled information report information sets 5760, handoffinformation 5762, uplink traffic request information 5764, and user data5766. The initial report control information includes size information5768 and time information 5770.

User/device/session/resource information 5738 includes information useridentification information, e.g., user log-in IDs, passwords and userpriority information, device information, e.g., device identificationinformation and device characteristic parameters, session information,e.g., information pertaining to peers, e.g., other WTs in communicationssessions with WT 5700, communications session information such assession keys, addressing and/or routing information, and resourceinformation, e.g., uplink and/or downlink air link segments and/oridentifiers allocated to the WT 5700.

System data/information 5740 includes a plurality of sets of basestation information (base station 1 data/information 5772, . . . , basestation M data/information 5774), recurring uplink reporting structureinformation 5780, and initial DCCH report information 5790. Base station1 data/information 5772 includes downlink timing/frequency structureinformation 5776 and uplink timing/frequency structure information 5778.Downlink timing/frequency structure information 5776 includes downlinklogical tone structure identifying various channels and segments, e.g.,assignment, beacon, pilot, downlink traffic channel, etc., in arepetitive downlink structure and identifying timing, e.g., OFDM symboltime duration, indexing, groupings of OFDM symbol times, e.g., intoslots, superslots, beaconslots, ultraslots, etc. Information 5776 alsoincludes base station identification information, e.g., cell, sector,and carrier/tone block identification information. Information 5776 alsoincludes downlink tone hopping information used to map logical tones tophysical tones. Uplink timing/frequency structure information 5778includes uplink logical tone structure identifying various channels andsegments, e.g., access, assignment, power control channels, timingcontrol channels, dedicated control channel (DCCH), uplink trafficchannel, etc., in a repetitive uplink structure and identifying timing,e.g., OFDM symbol time duration, indexing, groupings of OFDM symboltimes, e.g., into halfslots, slots, superslots, beaconslots, ultraslots,etc., as well as information correlating the downlink to uplink timingBS1, e.g., a timing offset between the uplink and downlink repetitivetiming structures at the base station. Information 5778 also includesuplink tone hopping information used to map logical tones to physicaltones.

Recurring uplink reporting structure information 5780 includes DCCHreports' format information 5782, and DCCH report sets information 5784.DCCH report sets information 5784 includes sets information 5786 andtime information 5788. For example, the recurring uplink reportingstructure information 5780 includes, in some embodiments, informationidentifying a recurring pattern of a fixed number of indexed DCCHsegments, e.g., 40 indexed DCCH segments. Each of the indexed DCCHsegments includes one of more types of DCCH reports, e.g., uplinktraffic channel request reports, interference reports such as beaconratio reports, different SNR reports, etc. The format of each of thedifferent types of reports is identified in DCCH reports' formatinformation 5782, e.g., for each type of report associating a fixednumber of information bits with different potential bit patterns andinterpretations of information conveyed by the corresponding bitpattern. DCCH report sets information 5784 identifies different groupingof reports associated with different indexed segments in the recurringDCCH reporting structure. Sets information 5786 identifies for eachindexed DCCH segment identified by a corresponding time informationentry 5788 a set of reports communicated in the segment and the order ofthose reports in the segment. For example in one exemplary embodiment,an exemplary DCCH segment with index value=6 includes 5 bit uplinktransmission power backoff report and a 1 bit uplink traffic channelsegment request report, while a DCCH segment with an index value=32includes a 3 bit downlink difference signal to noise ratio report and a3 bit uplink traffic channel request report. (See FIG. 10.)

Initial DCCH report information 5790 includes format information 5792and report set information 5794. The format information 5792 includesinformation indicating the format of initial reports sets to betransmitted. In some embodiments, the formats of the initial reports,groupings, and/or number of initial reports to be transmitted in aninitial report set depend on the time at which the initial report set isto be transmitted, e.g., with respect to a recurring uplink timingstructure. Report set information 5794 includes information identifyingvarious initial reports sets, e.g., number of reports, types of reports,and ordered grouping of reports, e.g., associated with DCCH segments tobe communicated in the initial report.

Base station identification information 5742 includes informationidentifying the base station attachment point being used by the wirelessterminal. Base station identification information 5742 includes physicalattachment point identifiers, e.g., cell, sector and carrier/tone blockidentifiers associated with the base station attachment point. In someembodiments, at least some of the base station identifier information iscommunicated via beacon signals. Base station identification information5742 also includes base station address information. Terminalidentification information 5744 includes base station assignedidentifiers associated with the wireless terminal, e.g., a registereduser identifier and a On state identifier, the On state identifier beingassociated with a logical DCCH tone to be used by the wireless terminal.Timing control information 5746 includes received downlink signals fromthe base station used by the timing control module 5732 for correlatingthe uplink reporting structure, at least some of the received downlinktiming control signals being used for closed loop timing control. Timingcontrol information 5746 also includes information identifying thecurrent timing with respect to repetitive uplink and downlink timingstructures, e.g., an OFDM symbol transmission time period with respectto the structures. Current state of operation information 5748 includesinformation identifying the wireless terminal's current state ofoperation, e.g., sleep, hold, ON. Current state of operation information5748 also includes information identifying when a WT is in a full-toneDCCH mode of operation or in a split-tone mode of DCCH operation, in anaccess process, or in the process of a handoff. In addition, currentstate of operation information 5748 includes, information identifyingwhether a wireless terminal is communicating an initial DCCH report setor communicating recurring reporting structure information DCCH reportsets, when the wireless terminal is assigned a logical DCCH channel toneto use. Initial report time information 5752 includes informationidentifying the point in time with respect to an uplink transmissionschedule at which the initial DCCH report set is to be transmitted.Determined initial report size information 5754 is an output of thereport set size determination sub-module 5736. Initial report controlinformation 5756 includes information used by the initial reportgeneration module 5728 to control the content of an initial report set.Initial report control information 5756 includes size information 5768and time information 5770. Generated initial report information set 5758is an initial report set generated by wireless terminal initial reportgeneration module 5728 using the data/information 5720 including initialDCCH report structure information 5790, initial report controlinformation 5756, and information to be included in the reports of theinitial report such as, e.g., uplink traffic channel request information5764, SNR information, and measured interference information. Generatedscheduled report information sets 5760 includes generated scheduledinformation report sets, e.g., each set corresponding to a scheduledDCCH segment to be used by the wireless terminal. The generatedscheduled report information sets 5760 being generated by the scheduledreport generation module 5730 using the data/information 5720 includingthe recurring uplink reporting structure information 5780, andinformation to be included in the reports of the initial report such as,e.g., uplink traffic channel request information 5764, SNR information,and measured interference information. Uplink traffic requestinformation 5764 includes information pertaining to requests for uplinktraffic channel segment resources, e.g., number of frames of uplink userdata to be communicated corresponding to different request group queues.User data 5766 includes, voice data, audio data, image data, text data,file data to be communicated via uplink traffic channel segments and/orreceived via downlink traffic channel segments.

FIG. 58 is a drawing of an exemplary base station 5800, e.g., accessnode, implemented in accordance with various embodiments. Exemplary basestation 5800 may be any of the base stations of the exemplary system ofFIG. 1. Exemplary base station 5800 includes a receiver module 5802, atransmitter module 5804, a processor 5806, an I/O interface 5808, and amemory 5810 coupled together via a bus 5812 over which the variouselements interchange data and information.

Receiver module 5802, e.g., an OFDM receiver, receives uplink signalsfrom a plurality of wireless terminals via receive antenna 5803. Theuplink signals include dedicated control channel report information setsfrom wireless terminals, access signals, requests for mode changes, anduplink traffic channel segment signals. Receiver module 5802 includes adecoder module 5814 for decoding uplink signals which were encoded priorto transmission by the wireless terminals.

Transmitter module 5804, e.g., an OFDM transmitter, transmits downlinksignals to wireless terminals via transmit antenna 5805. Transmitteddownlink signals include registration signals, DCCH control signals,traffic channel assignment signals, and downlink traffic channelsignals.

I/O interface 5808 provides an interface for coupling the base station5800 to other network nodes, e.g., other base stations, AAA servernodes, home agent nodes, routers, etc., and/or the Internet. I/Ointerface 5808 allows a wireless terminal using base station 5800 as itspoint of network attachment to communicate with peer nodes, e.g., otherwireless terminals, in different cells, via a backhaul communicationnetwork.

Memory 5810 includes routines 5820 and data/information 5822. Theprocessor 5806, e.g. a CPU, executes the routines 5820 and uses thedata/information 5822 in memory 5810 to control the operation of thebase station 5800 and implement methods. Routines 5820 include acommunications routines 5824 and base station control routines 5826. Thecommunications routines 5824 implement the various communicationsprotocols used by the base station 5800. Base station control routines5826 include a scheduler module 5828, a report set interpretation module5830, an access module 5832, a handoff module 5834, and a registeredwireless terminal state transition module 5836.

Scheduler module 5828 schedules uplink and/or downlink traffic channelsegments to wireless terminals, e.g., to wireless terminals which areusing the base station 5800 as their point of network attachment, are inan On state and currently have an assigned dedicated control channeleither in split-tone mode or full-tone mode.

Report set interpretation module 5830, e.g., a DCCH report setinterpretation module, includes an initial report set interpretationsub-module 5838 and a recurring reporting structure report setinterpretation sub-module 5840. Report set interpretation module 5830interprets each received DCCH report set in accordance with the initialDCCH report information 5850 or the recurring uplink reporting structureinformation 5848. Report set interpretation module 5830 is responsive totransitions by wireless terminals to the ON state. Report setinterpretation module 5830 interprets as an initial information reportset, a DCCH report information set received from a wireless terminalimmediately after one of: a migration of the wireless terminal to an Onstate from a hold state with respect to the current connection, amigration of the wireless terminal to an On state from an access statewith respect to the current connection, and a migration of the wirelessterminal to an On state from an On state which existed with respect toanother connection prior to a handoff to the base station. Report setinterpretation module 5830 includes an initial report set interpretationsub-module 5838 and a recurring reporting structure report setinterpretation sub-module 5840. Initial report set interpretationsub-module 5838 processes received information report sets, e.g.,corresponding to a received DCCH segment, which have been determined tobe an initial DCCH report set, using data/information 5822 includinginitial DCCH report information 5850, to obtain interpreted initialreport set information. Recurring reporting structure report setinterpretation sub-module 5840 processes received information reportsets, e.g., corresponding to a received DCCH segment, which have beendetermined to be a recurring reporting structure DCCH report set, usingdata/information 5822 including recurring uplink reporting structureinformation 5848, to obtain interpreted recurring structure report setinformation.

Access module 5832 controls operations relating to wireless terminalaccess operations. For example, a wireless terminal transitions throughthe access mode to an On state achieving uplink timing synchronizationwith a base station attachment point and receiving a WT On stateidentifier associated with a logical DCCH channel tone in the uplinktiming and frequency structure to be used to communicate uplink DCCHsegment signals. Following this transition to the On state, the initialreport set interpretation sub-module 5838 is activated to process DCCHsegments for the remainder of a superslot, e.g., one, two, three, four,or five DCCH segments, then operation is transferred to the recurringreporting structure report set interpretation sub-module 5840 to processsubsequent DCCH segments from the wireless terminal. The number of DCCHsegments and/or the format used for those segments processed by module5838 before transferring control to module 5840 is a function of thetime at which the access occurs with respect to the recurring uplinkDCCH reporting structure.

Handoff module 5834 controls operations pertaining to handoffs awireless terminal from one attachment point to another attachment point.For example, a wireless terminal in an ON state of operation with afirst base station attachment point may perform a handoff operation tobase station 5800 to transition into an ON state with respect to asecond base station attachment point, the second base station attachmentpoint being a base station 5800 attachment point, and the handoff module5834 activates the initial report set interpretation sub-module 5838.

Registered wireless terminal state transition module 5836 performsoperations related to mode changes of wireless terminals which haveregistered with the base station. For example, a registered wirelessterminal currently in a Hold state of operation in which the wirelessterminal is precluded from transmitting uplink user data may transitionto an On state of operation in which the WT is assigned an ON stateidentifier associated with a DCCH logical channel tone and in which thewireless terminal can receive uplink traffic channel segments which areto be used to communicate uplink user data. Registered WT statetransition module 5836 activates initial report set interpretationsub-module 5838 in response to the mode transition from Hold to ON ofthe wireless terminal.

Base station 5800 manages a plurality of ON state wireless terminals.For a set of received DCCH segments, communicated from differentwireless terminals, corresponding to the same time interval, the basestation, at some times, processes some of the segments using the initialreport set interpretation sub-module 5838 and some of the reports usingthe recurring reporting structure set interpretation sub-module 5840.

Data/information 5822 includes system data/information 5842, accesssignal information 5860, handoff signal information 5862, modetransition signaling information 5864, time information 5866, currentDCCH logical tone implementation information 5868, received DCCHsegments information 5870, base station identification information 5859,and WT data/information 5872.

System data/information 5842 includes downlink timing/frequencystructure information 5844, uplink timing/frequency structureinformation 5846, recurring uplink reporting structure information 5848,and initial DCCH report information 5850. Recurring uplink reportingstructure information 5848 includes DCCH reports' format information5852 and DCCH report sets information 5854. DCCH report sets information5854 includes sets information 5856 and time information 5858. InitialDCCH report information 5850 includes format information 5851 and reportset information 5853.

Downlink timing/frequency structure information 5844 includes downlinklogical tone structure identifying various channels and segments, e.g.,assignment, beacon, pilot, downlink traffic channel, etc., in arepetitive downlink structure and identifying timing, e.g., OFDM symboltime duration, indexing, groupings of OFDM symbol times, e.g., intoslots, superslots, beaconslots, ultraslots, etc. Information 5844 alsoincludes base station identification information, e.g., cell, sector,and carrier/tone block identification information. Information 5844 alsoincludes downlink tone hopping information used to map logical tones tophysical tones. Uplink timing/frequency structure information 5846includes uplink logical tone structure identifying various channels andsegments, e.g., access, assignment, power control channels, powercontrol channels, dedicated control channel (DCCH), uplink trafficchannel, etc., in a repetitive uplink structure and identifying timing,e.g., OFDM symbol time duration, indexing, groupings of OFDM symboltimes, e.g., into halfslots, slots, superslots, beaconslots, ultraslots,etc., as well as information correlating the downlink to uplink timing,e.g., a timing offset between the uplink and downlink repetitive timingstructures at the base station. Information 5846 also includes uplinktone hopping information used to map logical tones to physical tones.

Recurring uplink reporting structure information 5848 includes DCCHreports' format information 5852, and DCCH report sets information 5848.DCCH report sets information 5854 includes sets information 5856 andtime information 5858. For example, the recurring uplink reportingstructure information 5848 includes, in some embodiments, informationidentifying a recurring pattern of a fixed number of indexed DCCHsegments, e.g., 40 indexed DCCH segments. Each of the indexed DCCHsegments includes one of more types of DCCH reports, e.g., uplinktraffic channel request reports, interference reports such as beaconratio reports, different SNR reports, etc. The format of each of thedifferent types of reports is identified in DCCH reports' formatinformation 5852, e.g., for each type of report associating a fixednumber of information bits with different potential bit patterns andinterpretations of information conveyed by the corresponding bitpattern. DCCH report sets information 5854 identifies different groupingof reports associated with different indexed segments in the recurringDCCH reporting structure. Sets information 5856 identifies for eachindexed DCCH segment identified by a corresponding time informationentry 5858 a set of reports communicated in the segment and the order ofthose reports in the segment. For example in one exemplary embodiment,an exemplary DCCH segment with index value=6 includes 5 bit uplinktransmission power backoff report and a 1 bit uplink traffic channelsegment request report, while a DCCH segment with an index value=32includes a 3 bit downlink delta signal to node ratio report and a 3 bituplink traffic channel request report. (See FIG. 10.)

Initial DCCH report information 5850 includes format information 5851and report set information 5853. The format information 5851 includesinformation indicating the format of initial reports sets to betransmitted. In some embodiments, the formats of the initial reports,groupings, and/or number of initial reports to be transmitted in aninitial report set depend on the time at which the initial report set isto be transmitted, e.g., with respect to a recurring uplink timingstructure. Report set information 5853 includes information identifyingvarious initial reports sets, e.g., number of reports, types of reports,and ordered grouping of reports, e.g., associated with DCCH segments tobe communicated in the initial report set.

Base station identification information 5859 includes informationidentifying the base station attachment point being used by the wirelessterminal. Base station identification information 5859 includes physicalattachment point identifiers, e.g., cell, sector and carrier/tone blockidentifiers associated with the base station attachment point. In someembodiments, at least some of the base station identifier information iscommunicated via beacon signals. Base station identification informationalso includes base station address information. Access signalinformation 5860 includes access request signals received from wirelessterminals, access response signals sent to wireless terminal, timingsignals related to the access, and base station internal signaling toactivate the initial report interpretation sub-module 5838 in responseto a transition from the access state to the On state for a wirelessterminal. Handoff signal information 5862 includes informationpertaining to handoff operations including handoff signaling receivedfrom other base stations and base station internal signaling to activatethe initial report interpretation sub-module 5838 in response to atransition from a WT ON state of another connection to a WT On statewith respect to a base station 5800 attachment point connection. Modetransitioning signaling information 5864 includes signals between acurrently registered wireless terminal and base station 5800 regardingstate changes, e.g., a change from hold state to On state, and basestation internal signaling to activate the initial report setinterpretation sub-module 5838 in response to state transitions, e.g.,Hold to On. Registered WT state transition module 5836 also deactivatesrecurring reporting structure report set interpretation sub-module 5840with respect to a wireless terminal in response to some state changes,e.g., a wireless terminal transition from ON state to one of Hold state,sleep state, or Off state.

Time information 5866 includes current time information, e.g., anindexed OFDM symbol time period within a recurring uplink timingstructure being used by the base station. Current DCCH logical toneimplementation information 5868 includes information identifying whichof the base stations logical DCCH tones are currently in a full-toneDCCH mode and which are in a split-tone DCCH mode. Received DCCHsegments information 5860 includes information from received DCCHsegments corresponding to a plurality of WT users currently assignedlogical DCCH tones.

WT data/information 5872 includes a plurality of sets of wirelessterminal information (WT 1 data/information 5874, . . . , WT Ndata/information 5876). WT 1 data/information 5874 includesidentification information 5886, mode information 5888, received DCCHinformation 5880, processed DCCH information 5882, and user data 5884.Received DCCH information 5880 includes initial received report setinformation 5892 and recurring report structure received report setsinformation 5894. Processed DCCH information 5882 includes interpretedinitial report set information 5896 and interpreted recurring structurereport sets information 5898. Identification information 5886 includes abase station assigned wireless terminal registration identifier,addressing information associated with WT1. At times, the identificationinformation 5886 includes a WT On state identifier, the On stateidentifier associated with a logical DCCH channel tone to be used by thewireless terminal to communicate DCCH segment signals. Mode information5888 includes information identifying the current state of WT1, e.g.,sleep state, Hold state, access state, On state, in the process of ahandoff, etc., and information further qualifying the ON state, e.g.,full tone DCCH On or split-tone DCCH On. User data 5884 includes uplinkand/or downlink traffic channel segment information, e.g., voice data,audio data, image data, text data, file data, etc., to be receivedfrom/communicated to a peer node of WT1 in a communications session withWT1.

Initial received report set information 5892 includes a set ofinformation corresponding to a WT1 DCCH segment which was communicatedusing format in accordance with an initial reporting information 5850and is interpreted by module 5838 recovering interpreted initial reportinformation set information 5896. Recurring report structure receivedreport sets information 5894 includes a set of information correspondingto a WT1 DCCH segment which was communicated using format in accordancewith recurring uplink reporting structure information 5848 and isinterpreted by module 5840 recovering a interpreted recurring reportinformation set information 5898.

FIG. 59 comprising the combination of FIG. 59A, FIG. 59B and FIG. 59C isa flowchart 5900 of an exemplary method of operating a wireless terminalin accordance with various embodiments. The exemplary method starts instep 5901 where the wireless terminal is powered up and initialized.Operation proceeds from step 5901 to steps 5902 and step 5904. In step5902, the wireless terminal tracks, on an ongoing basis, current time inrelation to an uplink recurring DCCH reporting schedule and in relationto uplink tone hopping information. Time information 5906 is output fromstep 5902 to be used in other steps of the method.

In step 5904, the wireless terminal receives a base station On stateidentifier associated with a DCCH logical tone in an uplink channelstructure of an access node serving as the wireless terminal's point ofattachment. Operation proceeds from step 5904 to step 5908. In step5908, the wireless terminal receives information identifying whether thewireless terminal should be in a full-tone DCCH mode of operation or asplit-tone DCCH mode of operation, said information indicatingsplit-tone DCCH mode of operation also identifying one among a pluralityof sets of DCCH segments associated with the DCCH logical tone. Forexample, in an exemplary embodiment, when in full-tone DCCH mode, awireless terminal is allocated a single logical DCCH tone corresponds toa recurring set of 40 indexed DCCH segments in an uplink channelstructure, but while in a split-tone mode of operation, a wirelessterminal is allocated a single logical DCCH tone which is time sharedsuch that the wireless terminal receives a set of 13 indexed segments ina recurring uplink channel structure and two other wireless terminalsmay each be allocated a different set of 13 segments in the uplinkchannel structure. In some embodiments the information communicated insteps 5904 and 5908 are communicated in the same message. Operationproceeds from step 5908 to step 5910.

In step 5910, the wireless terminal proceeds to step 5912 if thewireless terminal has determined that it in full-tone DCCH mode, whileoperation proceeds to step 5914 if the wireless terminal has determinedthat it in split-tone DCCH mode.

In step 5912, the wireless terminal identifies DCCH communicationsegments allocated to the wireless terminal using time information 5906and the identified logical DCCH tone. For example, in an exemplaryembodiment, for each beacon slot, the wireless terminal identifies a setof 40 indexed DCCH segments corresponding to assigned logical DCCH tone.Operation proceeds from step 5912 to step 5916, for each identifiedcommunications segment. In step 5916, the wireless terminal using timeinformation 5906, the indexed value of the DCCH segment within therecurring structure, and stored information associating sets of reporttypes with each indexed segment, identifies a set of report types to becommunicated in the DCCH communications segment. Operation proceeds fromstep 5916 via connecting node A 5920 to step 5924.

In step 5924, the wireless terminal checks as to whether any of reporttypes identified in step 5916 include a flexible report. If any of theidentified report types indicate a flexible report, then operationproceeds from step 5924 to step 5928; otherwise operation proceeds fromstep 5924 to step 5926.

In step 5926, the wireless terminal, for each fixed type informationreport of the segment, maps the information to be conveyed to a fixednumber of information bits corresponding to the report size, said fixedtype of information reports being dictated by a reporting schedule.Operation proceeds from step 5926 to step 5942.

In step 5928, the wireless terminal selects which type of report fromamong a plurality of fixed type information report types to include as aflexible report body. Step 5928 includes sub-step 5930. In sub-step5930, the wireless terminal performs the selection as a function of areport prioritization operation. Sub-step 5930 includes sub-step 5932and 5934. In sub-step 5932, the wireless terminal considers the amountof uplink data queued for communication to the access node, e.g., thebacklog in a plurality of request queues, and at least one signalinterference measurement, e.g., a beacon ratio report. In sub-step 5934,the wireless terminal determines an amount of change in informationpreviously reported in at least one report, e.g., a measured change in adownlink saturation level of self-noise SNR report. Operation proceedsfrom step 5928 to step 5936.

In step 5936, the wireless terminal codes the type of flexible bodyreport into a type identifier, e.g., a two bit flexible report bodyidentifier. Operation proceeds from step 5936 to step 5938. In step5938, the wireless terminal maps the information to be conveyed in theflexible report body in accordance with the selected report type to anumber of information bits corresponding to the flexible report bodysize. Operation proceeds from step 5938 to either step 5940 or step5942. Step 5942 is an optional step, included in some embodiments. Instep 5940, for each fixed type information report of the segment inaddition to the flexible report, map the information to be conveyed to afixed number of information bits corresponding to the report size.Operation proceeds from step 5940 to step 5942. For example, in someembodiments, a DCCH segment including a flexible report, when in thefull-tone mode utilizes the full number of information bits communicatedby the segment for itself, e.g., the segment conveys 6 information bits,2 bits are used for identifying the type of report and 4 bits used forconveying the body of the report. In such an embodiment, step 5940 isnot performed. In some other embodiments, the total number of bitsconveyed by a DCCH segment in the full-tone DCCH mode is greater thanthe number of bits represented by the flexible report and step 5940 isincluded to utilize the remaining information bits of the segment. Forexample, the segment conveys a total of 7 information bits 6 of whichare utilized by the flexible report and 1 is used for a fixed oneinformation bit uplink traffic request report.

In step 5942, the wireless terminal performs coding and modulationoperations to generate a set of modulation symbols to represent the oneor more reports to be communicated in the DCCH segment. Operationproceeds from step 5942 to step 5944. In step 5944, the wirelessterminal, for each modulation symbol of the set of generated modulationsymbols determines, using time information 5906 and tone hoppinginformation, the physical tone to be used to convey the modulationsymbol. For example, in an exemplary embodiment, each DCCH segmentcorresponds to 21 OFDM tone-symbols each tone symbol being used toconvey one QPSK modulation symbol, each of the 21 OFDM tone-symbolscorresponding to the same logical DCCH tone; however due to uplink tonehopping, 7 OFDM tone symbols in a first set of seven successive OFDMsymbol time periods corresponding to a first physical tone, a second setof seven OFDM tone-symbols in a second set of seven successive OFDMsymbol time periods corresponding to a second physical tone, and a thirdset of seven successive OFDM symbol time periods corresponding to athird physical tone, the first second and third physical tones beingdifferent. Operation proceeds from step 5944 to step 5946. In step 5946,the wireless terminal transmits each modulation symbol of the DCCHsegment using the determined corresponding physical tone.

Returning to step 5914, in step 5914, the wireless terminal identifiesDCCH communication segments allocated to the wireless terminal usingtime information 5906, the identified logical DCCH tone, and theinformation identifying the one among the plurality of sets of DCCHsegments. For example, in an exemplary embodiment, for each beacon slot,the wireless terminal identifies a set of 13 indexed DCCH segmentscorresponding to assigned logical DCCH tone. Operation proceeds fromstep 5914 to step 5918, for each identified DCCH communications segment.In step 5918, the wireless terminal using time information 5906, theindexed value of the DCCH segment within the recurring structure, andstored information associating sets of report types with each indexedsegment, identifies a set of report types to be communicated in the DCCHcommunications segment. Operation proceeds form step 5916 via connectingnode B 5922 to step 5948.

In step 5948, the wireless terminal checks as to whether any of reporttypes identified in step 5918 include a flexible report. If any of theidentified report types indicate a flexible report, then operationproceeds from step 5948 to step 5952; otherwise operation proceeds fromstep 5948 to step 5950.

In step 5950, the wireless terminal, for each fixed type informationreport of the segment, maps the information to be conveyed to a fixednumber of information bits corresponding to the report size, said fixedtype of information reports being dictated by a reporting schedule.Operation proceeds from step 5950 to step 5966.

In step 5952, the wireless terminal selects which type of report fromamong a plurality of fixed type information report types to include as aflexible report body. Step 5952 includes sub-step 5954. In sub-step5954, the wireless terminal performs the selection as a function of areport prioritization operation. Sub-step 5954 includes sub-step 5956and 5958. In sub-step 5956, the wireless terminal considers the amountof uplink data queued for communication to the access node, e.g., thebacklog in a plurality of request queues, and at least one signalinterference measurement, e.g., a beacon ratio report. In sub-step 5958,the wireless terminal determines an amount of change in informationpreviously reported in at least one report, e.g., a measured change in adownlink saturation level of self-noise SNR report. Operation proceedsfrom step 5952 to step 5960.

In step 5960, the wireless terminal codes the type of flexible bodyreport into a type identifier, e.g., a single bit flexible report bodyidentifier. Operation proceeds from step 5960 to step 5962. In step5962, the wireless terminal maps the information to be conveyed in theflexible report body in accordance with the selected report type to anumber of information bits corresponding to the flexible report bodysize. Operation proceeds from step 5962 to either step 5964 or step5966. Step 5964 is an optional step, included in some embodiments. Instep 5964, for each fixed type information report of the segment inaddition to the flexible report, map the information to be conveyed to afixed number of information bits corresponding to the report size.Operation proceeds from step 5964 to step 5966. For example, in someembodiments, a DCCH segment including a flexible report, when in thesplit-tone mode utilizes the full number of information bitscommunicated by the segment for itself, and in such an embodiment, step5964 is not performed. In some other embodiments, the total number ofbits conveyed by a DCCH segment in the split-tone DCCH mode is greaterthan the number of bits represented by the flexible report and step 5940is included to utilize the remaining information bits of the segment.For example, the segment conveys a total of 8 information bits 6 ofwhich are utilized by the flexible report and 1 information bit is usedfor a fixed one information bit uplink traffic request report, and 1information bit is used for another predetermined report type. In someembodiments, the size of the body of the flexible report variescorresponding to different selections of the type of report to beconveyed by the flexible report, e.g., a 4 bit uplink traffic channelrequest or a five bit uplink transmission power backoff report, and theremainder of the available bits in the segment can be allocated topredetermined fixed report types, e.g., 1 or 2 bits.

In step 5966, the wireless terminal performs coding and modulationoperations to generate a set of modulation symbols to represent the oneor more reports to be communicated in the DCCH segment. Operationproceeds from step 5966 to step 5968. In step 5968, the wirelessterminal, for each modulation symbol of the set of generated modulationsymbols determines, using time information 5906 and tone hoppinginformation, the physical tone to be used to convey the modulationsymbol. For example, in an exemplary embodiment, each DCCH segmentcorresponds to 21 OFDM tone-symbols each tone symbol being used toconvey one QPSK modulation symbol, each of the 21 OFDM tone-symbolscorresponding to the same logical DCCH tone; however due to uplink tonehopping, 7 OFDM tone symbols in a first set of seven successive OFDMsymbol time periods corresponding to a first physical tone, a second setof seven OFDM tone-symbols in a second set of seven successive OFDMsymbol time periods corresponding to a second physical tone, and a thirdset of seven successive OFDM symbol time periods corresponding to athird physical tone, the first second and third physical tones beingdetermined in accordance with tone hopping information and may bedifferent. Operation proceeds from step 5968 to step 5970. In step 5970,the wireless terminal transmits each modulation symbol of the DCCHsegment using the determined corresponding physical tone.

FIG. 60 is a flowchart 6000 of an exemplary method of operating awireless terminal to provide transmission power information to a basestation in accordance with various embodiments. Operation starts in step6002. For example, the wireless terminal may have been previouslypowered on, established a connection with a base station, havetransitioned in the ON state of operation, and been assigned dedicatedcontrol channel segments to use in either a full-tone or split tone modeof DCCH operation. The full-tone DCCH mode of operation is in someembodiments, a mode in which the wireless tone is dedicated a singlelogical tone channel used for DCCH segments which is not shared withother wireless terminal, while the split tone-DCCH mode of operation is,in some embodiments, a mode in which the wireless terminal is dedicateda portion of a single logical DCCH tone channel which can be allocatedto be used on a time shared with another wireless terminal or terminals.Operation proceeds from start step 6002 to step 6004.

In step 6004, the wireless terminal generates a power report indicatinga ratio of a maximum transmit power of the wireless terminal to thetransmit power of a reference signal having a power level known to thewireless terminal at a point in time corresponding to the power report.In some embodiments the power report is a backoff report, e.g., awireless terminal transmission power backoff report, indicating a dBvalue. In some embodiments, the maximum transmission power value dependson a power output capability of the wireless terminal. In someembodiments, the maximum transmission power is specified by a governmentregulation limiting the maximum output power level of the wirelessterminal. In some embodiments, the reference signal is controlled by thewireless terminal based upon at least one closed loop power levelcontrol signal received from a base station. In some embodiment, thereference signal is a control information signal transmitted over adedicated control channel to the base station. The reference signal, insome embodiments, is measured for received power level by the basestation to which it is transmitted. In various embodiments, thededicated control channel is a single tone control channel whichcorresponds to a single logical tone dedicated to the wireless terminalfor use in transmitting control information. In various embodiments, thepower report is a power report corresponding to a single instant intime. In some embodiments, the known reference signal is a signaltransmitted on the same channel as the power report, e.g., the same DCCHchannel. In various embodiments, the point in time to which a generatedpower report corresponds has a known offset from a start of acommunication segment, e.g., a DCCH segment, in which said power reportis to be transmitted. Step 6004 includes sub-step 6006, sub-step 6008,sub-step 6010, and sub-step 6012.

In sub-step 6006, the wireless terminal performs a subtraction operationincluding subtracting a per-tone transmission power of an uplinkdedicated control channel in dBm from a maximum transmission power ofwireless terminal in dBm. Operation proceeds from sub-step 6006 tosub-step 6008. In sub-step 6008, the wireless terminal proceeds todifferent sub-steps depending upon whether the wireless terminal is in afull-tone DCCH mode of operation or a split-tone DCCH mode of operation.If the wireless terminal is in full-tone DCCH mode of operation,operation proceeds from sub-step 6008 to sub-step 6010. If the wirelessterminal is in split-tone DCCH mode of operation, operation proceedsfrom sub-step 6008 to sub-step 6012. In sub-step 6010, the wirelessterminal generates a power report in accordance with a first format,e.g., a 5 information bit power report. For example the result ofsub-step 6006 is compared to a plurality of different levels, each levelcorresponding to a different 5 bit pattern, the level closet to theresult of sub-step 6006 is selected for the report, and the bit patterncorresponding to that level is used for the report. In one exemplaryembodiment, the levels range from 6.5 dBs to 40 dBs. (See FIG. 26.) Insub-step 6012 the wireless terminal generates a power report inaccordance with a second format, e.g., a 4 information bit power report.For example the result of sub-step 6006 is compared to a plurality ofdifferent levels, each level corresponding to a different 4 bit pattern,the level closet to the result of sub-step 6006 is selected for thereport, and the bit pattern corresponding to that level is used for thereport. In one exemplary embodiment, the levels range from 6 dBs to 36dBs. (See FIG. 35.) Operation proceeds from step 6004 to step 6014.

In step 6014, the wireless terminal is operated to transmit thegenerated power report to a base station. Step 6014 includes sub-steps6016, 6018, 6020, 6022, and 6028. In sub-step 6016, the wirelessterminal proceeds to different sub-steps depending upon whether thewireless terminal is in a full-tone DCCH mode of operation or asplit-tone DCCH mode of operation. If the wireless terminal is infull-tone DCCH mode of operation, operation proceeds from sub-step 6016to sub-step 6018. If the wireless terminal is in split-tone DCCH mode ofoperation, operation proceeds from sub-step 6016 to sub-step 6020.

In sub-step 6018, the wireless terminal combines the generated powerreport with additional information bit(s), e.g., 1 additionalinformation bit, and jointly codes the set of combined information bits,e.g., set of 6 information bits, to generate a set of modulation symbolsfor a DCCH segment, e.g., a set of 21 modulation symbols. For example,the 1 additional information bit is, in some embodiments, a singleinformation bit uplink traffic channel resource request report. Insub-step 6020, the wireless terminal combines the generated power reportwith additional information bit(s), e.g., 4 additional information bits,and jointly codes the set of combined information bits, e.g., set of 8information bits, to generate a set of modulation symbols for a DCCHsegment, e.g., a set of 21 modulation symbols. For example, the set of 4additional information bit is, in some embodiments, a 4 information bituplink traffic channel resource request report. Operation proceeds fromsub-step 6018 or sub-step 6020 to sub-step 6022.

In sub-step 6022, the wireless terminal determines the single OFDM toneused during each of a plurality of consecutive OFDM symbol transmissiontime periods for the DCCH segment. Sub-step 6022 includes sub-step 6024and sub-step 6026. In sub-step 6024, the wireless terminal determinesthe logical DCCH channel tone assigned to the wireless terminal, and insub-step 6026, the wireless terminal determines a physical tone to whichthe logical DCCH channel tone corresponds at different points in timebased on tone hopping information. For example, in some embodiments, anexemplary DCCH segment corresponds to a single DCCH channel logical toneand the DCCH segment includes 21 OFDM tone-symbols, one OFDM tone-symbolfor each of the 21 consecutive OFDM symbol transmission time intervals,the same physical tone used for a first set of seven, a second physicaltone used for a second set of seven, and a third physical tone used fora third set of seven. Operation proceeds from sub-step 6022 to sub-step6028. In sub-step 6028, the wireless terminal, for each OFDM symboltransmission time period, corresponding to the DCCH segment, transmits amodulation symbol from the set of generated modulation symbols using thedetermined physical tone for that point in time.

Operation proceeds from step 6014 to step 6004, where the wirelessterminal proceeds to generate another power report. In some embodiments,the power report is transmitted twice during each recurring cycle of adedicated control channel reporting structure used to controltransmission of control information by the wireless terminal. In someembodiments, the power report is transmitted, on average at least onceevery 500 OFDM symbol transmission time periods but on average atintervals spaced apart by at least 200 symbol transmission timeintervals.

Various features of an exemplary embodiment will now be described. Thewireless terminal (WT) uses an ULRQST1, ULRQST3 or ULRQST4 to report thestatus of the MAC frame queues at the WT transmitter.

The WT transmitter maintains MAC frame queues, which buffers the MACframes to be transmitted over the link. The MAC frames are convertedfrom the LLC frames, which are constructed from packets of upper layerprotocols. An uplink user data packet belongs to one of 4 requestgroups. A packet is associated with a particular request group. If thepacket belongs to one request group, then each of the MAC frames of thatpacket also belong to that request group.

The WT reports the number of MAC frames in the 4 request groups that theWT may intend to transmit. In the ARQ protocol, those MAC frames aremarked as “new” or “to be retransmitted”.

The WT maintains a vector of four elements N[0:3]: for k=0:3, N[k]represents the number of MAC frames that the WT intends to transmit inrequest group k. The WT reports the information about N[0:3] to the basestation sector (BSS) so that the BSS can utilize the information in anuplink (UL) scheduling algorithm to determine the assignment of uplinktraffic channel (UL.TCH) segments.

In an exemplary embodiment, the WT uses the single bit uplink trafficchannel request report (ULRQST1) to report N[0]+N[1] according to table6100 of FIG. 61. Table 6100 is an exemplary format for an ULRQST1report. First column 6102 indicates the two possible bit patterns thatmay be conveyed while second column 6104 indicates the meaning of eachbit pattern. If the bit pattern is 0, that indicates that there are noMAC frames that the WT intends to transmit in either request group 0 orrequest group 1. If the bit pattern is 1, that indicates that the WT hasat least one MAC frame in request group 0 or request group 1 that the WTintends to communicate.

At a given time, the WT uses only one request dictionary. When the WTjust enters the ACTIVE state, the WT uses the default requestdictionary. To change the request dictionary, the WT and the BSS uses anupper layer configuration protocol. When the WT migrates from the ONstate to the HOLD state, the WT keeps the last request dictionary usedin the ON state so that when the WT migrates from the HOLD state to theON state later, the WT continues to use the same request dictionaryuntil the request dictionary is explicitly changed. However, if the WTleaves the ACTIVE state, then the memory of the last request dictionaryused is cleared.

To determine an ULRQST3 or ULRQST4, the WT first calculates thefollowing two parameters, y and z, and then use one of the followingdictionaries. Denote by x the value (in dB) of the most recent 5 bituplink transmission power backoff report (ULTXBKF5) report, and by b₀the value in (dB) of the most recent generic 4 bit downlink beacon ratioreport (DLBNR4). The WT further determines an adjusted generic DLBNR4report value b as follows: b=b₀−ulTCHrateFlashAssignmentOffset, whereminus is defined in the dB sense. The base station sector broadcasts thevalue of ulTCHrateFlashAssignmentOffset in a downlink broadcast channel.The WT uses ulTCHrateFlashAssignmentOffset equal to 0 dB until the WTreceives the value from the broadcast channel.

FIG. 62 is an exemplary table 6200 used to calculate control parametersy and z. First column 6202 lists a condition; second column 6204 liststhe corresponding value of output control parameter y; third column 6206lists the corresponding value of output control parameter z. Given x andb, the WT determines y and z as those from the first row in Table 6200of FIG. 62 for which the condition in the first column is satisfied. Forexample, if x=17 and b=3, then z=min(4,N_(max)) and y=1. Denote R_(max)the highest rate option that the WT can support, and N_(max) the numberof MAC frames of that highest rate option.

The WT uses an ULRQST3 or ULRQST4 to report the actual N[0:3] of the MACframe queues according to a request dictionary. A request dictionary isidentified by a request dictionary (RD) reference number.

The exemplary request dictionaries show that any ULRQST4 or ULRQST3report may not completely include the actual N[0:3]. A report is ineffect a quantized version of the actual N[0:3]. A general guideline isthat the WT should send a report to minimize the discrepancy between thereported and the actual MAC frames queues first for request groups 0 and1, and then for request group 2, and finally for request group 3.However, the WT has the flexibility of determining a report to benefitthe WT the most. For example, when the WT is using the requestdictionary 2, the WT may use an ULRQST4 to report N[1]+N[3] and use anULRQST3 to report N[2]. In addition, if a report is directly related toa subset of request groups according to the request dictionary, it doesnot automatically imply that the MAC frame queues of a remaining requestgroup are empty. For example, if a report means N[2]=1, then it may notautomatically imply that N[0]=0, N[1]=0, or N[3]=0.

Table 6300 of FIG. 63 and Table 6400 of FIG. 64 define an exemplaryrequest dictionary with the RD reference number equal to 0. Defined₁₂₃=ceil(((N[1]+N[2]+N[3]−N_(123,min))/(y*g)), where N_(123,min) and gare variables determined by the most recent ULRQST4 report as per Table6300. FIG. 63 is a table 6300 identifying bit format and interpretationsassociated with each of 16 bit patterns for a four bit uplink request,ULRQST4, corresponding to an exemplary first request dictionary (RDreference number=0). In some embodiments, the request dictionary withreference number=0 is the default request dictionary. First column 6302identifies the bit pattern and bit ordering, most significant bit toleast significant bit. Second column 6304 identifies the interpretationassociated with each bit pattern. FIG. 64 is a table 6400 identifyingbit format and interpretations associated with each of 8 bit patternsfor a three bit uplink request, ULRQST3, corresponding to an exemplaryfirst request dictionary (RD reference number=0). In some embodiments,the request dictionary with reference number=0 is the default requestdictionary. First column 6402 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column6404 identifies the interpretation associated with each bit pattern.

Table 6500 of FIG. 65 and Table 6600 of FIG. 66 define an exemplaryrequest dictionary with the RD reference number equal to 1. FIG. 65 is atable 6500 identifying bit format and interpretations associated witheach of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary second request dictionary (RD referencenumber=1). First column 6502 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column6504 identifies the interpretation associated with each bit pattern.FIG. 66 is a table 6600 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary second request dictionary (RDreference number=1). First column 6602 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 6604 identifies the interpretation associated with each bitpattern.

Table 6700 of FIG. 67 and Table 6800 of FIG. 68 define an exemplaryrequest dictionary with the RD reference number equal to 2. FIG. 67 is atable 6700 identifying bit format and interpretations associated witheach of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary third request dictionary (RD referencenumber=2). First column 6702 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column6704 identifies the interpretation associated with each bit pattern.FIG. 68 is a table 6800 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary third request dictionary (RDreference number=2). First column 6802 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 6804 identifies the interpretation associated with each bitpattern.

Table 6900 of FIG. 69 and Table 7000 of FIG. 70 define an exemplaryrequest dictionary with the RD reference number equal to 3. FIG. 69 is atable 6900 identifying bit format and interpretations associated witheach of 16 bit patterns for a four bit uplink request, ULRQST4,corresponding to an exemplary fourth request dictionary (RD referencenumber=3). First column 6902 identifies the bit pattern and bitordering, most significant bit to least significant bit. Second column6904 identifies the interpretation associated with each bit pattern.FIG. 70 is a table 7000 identifying bit format and interpretationsassociated with each of 8 bit patterns for a three bit uplink request,ULRQST3, corresponding to an exemplary fourth request dictionary (RDreference number=3). First column 7002 identifies the bit pattern andbit ordering, most significant bit to least significant bit. Secondcolumn 7004 identifies the interpretation associated with each bitpattern.

FIG. 71 is a drawing of an exemplary wireless terminal 7100, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary WT 7100 may be any of the wireless terminals of the exemplarysystem of FIG. 1. Exemplary WT 7100 may be any of the WTs (136, 138,144, 146, 152, 154, 168, 170, 172, 174, 176, 178) of exemplary system100 of FIG. 1. Exemplary wireless terminal 7100 includes a receivermodule 7102, a transmitter module 7104, a processor 7106, user I/Odevices 7108, and a memory 7110 coupled together via a bus 7112 viawhich the various elements may interchange data and information.

Memory 7110 includes routines 7118 and data/information 7120. Theprocessor 7106, e.g., a CPU, executes the routines 7118 and uses thedata/information 7120 in memory 7110 to control the operation of thewireless terminal 7100 and implement methods.

Receiver module 7102, e.g., an OFDM receiver, is coupled to receiveantenna 7103 via which the wireless terminal 7100 receives downlinksignals from base stations. Receiver module 7102 includes a decoder 7114which decodes at least some of the received downlink signals.Transmitter module 7104, e.g., an OFDM transmitter, is coupled to atransmit antenna 7105 via which the wireless terminal 7100 transmitsuplink signals to base stations. Transmitter module 7104 is used fortransmitting a plurality of different types of fixed reports usinguplink dedicated control channel segments dedicated to the wirelessterminal. Transmitter module 7104 is also used for transmitting flexiblereports using uplink dedicated control channel segments dedicated to thewireless terminal, the uplink DCCH segments which include a flexiblereport being the same size as at least some of the uplink DCCH segmentswhich include fixed type reports and do not include a flexible report.Transmitter module 7104 includes an encoder 7116 which is used to encodeat least some of the uplink signals prior to transmission. In someembodiments, each individual dedicated control channel uplink segment isencoded independently of other dedicated control channel uplinksegments. In various embodiments, the same antenna is used for both thetransmitter and receiver.

User I/O devices 7108, e.g., microphone, keyboard, keypad, switches,camera, speaker, display, etc., are used to input/output user data,control applications, and control the operation of the wirelessterminal, e.g., allowing a user of WT 7100 to initiate a communicationssession.

Routines 7118 includes a communications routine 7122 and wirelessterminal control routines 7124. Communications routine 7122 performsvarious communications protocols used by wireless terminal 7100.Wireless terminal control routines 7124 include a fixed type reportcontrol module 7126, a flexible type report control module 7128, anuplink tone hopping module 7130, an identifier module 7132, and a codingmodule 7134.

Fixed type report control module 7126 controls the transmission of aplurality of different types of fixed type information reports accordingto a reporting schedule, said fixed type information reports being of atype dictated by the reporting schedule.

Flexible type report control module 7128 controls transmission offlexible reports at predetermined locations in the reporting schedule,said flexible type reports being of report types selected by theflexible report control module from a plurality of reports which can bereported using a flexible report. Flexible report control module 7128includes a report prioritization module 7136. The report prioritizationmodule 7136 takes into consideration the amount of uplink data queuedfor communication to the base station and a least one signalinterference measurement, when determining which one of a plurality ofalternative reports should be communicated in a flexible report. Reportprioritization module 7138 also includes a change determination module7138, which determines an amount of change in information previouslyreported in at least one report. For example, if the changedetermination module 7138 determines that the value of saturation levelof SNR indicative of WT self-noise has not changed significantly fromthe last reported value, but the demand for uplink traffic channelresources has significantly increased from the last reported request,the wireless terminal 7100 may select to use the flexible report tocommunicate an uplink traffic channel request report instead of asaturation level of SNR report.

Uplink tone hopping module 7130 determines, based on stored tone hoppinginformation, for transmission purposes, the physical tone correspondingto the logical assigned DCCH channel tone at different points in timecorresponding to the transmission of dedicated segments. For example, inone exemplary embodiment, a DCCH segment corresponds to three dwells,each dwell using the same physical tone for seven successive OFDM symboltransmission time intervals; however, the physical tone associated withthe different dwells is determined by tone hopping information and maybe different.

Identifier module 7132 generates flexible type report identifiers to becommunicated with flexible reports, the report type identifierscommunicated with an individual flexible report indicating the type offlexible report being communicated. In various embodiments, theidentifier module 7132 generates a report which indicates the type offlexible report which corresponds to the report type identifier. In thisexemplary embodiment, an individual flexible type report is communicatedin the same DCCH segment with the corresponding report type identifier.In this exemplary embodiment, identifier module 7132 is not used forfixed type reports as there is a predetermined understanding between thebase station and wireless terminal as to the type of fixed report beingcommunicated based on position of the fixed report within the recurringreporting structure.

Coding module 7134 codes an individual flexible report identifier and acorresponding flexible report together in a single coding unitcorresponding to the DCCH communications segment in which they aretransmitted. In some embodiments, coding module 7134 operates inconjunction with encoder 7116.

Data/information 7120 includes user/device/session/resource information7140, system data/information 7142, generated fixed type report 1 7144,. . . , generated fixed type report n 7146, selected type of flexiblereport 7148, generated flexible report 7150, flexible report typeidentifier 7152, coded DCCH segment information 7154, DCCH channelinformation 7156 including assigned logical tone information 7158, basestation identification information 7160, terminal identificationinformation 7162, timing information 7164, amount of uplink data queued7166, signal interference information 7168, and report changeinformation 7170. Assigned logical tone information 7158 identifies abase station assigned single logical uplink dedicated control channeltone to be used by the WT 7100 for communicating uplink DCCH segmentsignals conveying fixed and flexible reports. In some embodiments, thesingle assigned logical DCCH tone is associated with a base stationassigned ON state identifier.

User/device/session/resource information 7140 includes informationpertaining to communications sessions, e.g., peer node information,addressing information, routing information, state information, andresource information identifying uplink and downlink air link resources,e.g., segments, allocated to WT 7100. Generated fixed type of report 17144 is a fixed type report corresponding to one of the plurality offixed types of reports supported by WT 7100 and has been generated usingfixed type report information 7188. Generated fixed type of report n7146 is a fixed type report corresponding to one of the plurality offixed types of reports supported by WT 7100 and has been generated usingfixed type report information 7188. Selected type of flexible report7148 is information identifying the wireless terminal's selection forthe type of report to be communicated in the flexible report, e.g., apattern of two bits identifying one of four patterns corresponding to aTYPE 2 report of FIG. 31. Generated flexible report 7150 is a flexibletype report corresponding to one of the plurality of types of reportswhich may be selected by WT 7100 to be communicated in a flexible reportand has been generated using flexible type report information 7190,e.g., a pattern of four bits corresponding to a BODY 4 report andrepresenting a bit pattern of one of an ULRQST4 report, e.g., of FIG.18, or a DLSSNR4 report of FIG. 30. Coded DCCH segment information 7154is an output of coding module 7134, e.g., a coded DCCH segmentcorresponding to a Type 2 and Body 4 report or a coded DCCH segmentcorresponding to a mixture of fixed type reports.

DCCH channel information 7156 includes information identifying DCCHsegments allocated to WT 7100, e.g., information identifying a DCCH modeof operation, e.g., a full-tone DCCH mode or a split tone DCCH mode andinformation identifying an assigned logical DCCH tone 7158 in a DCCHchannel structure being used by the base station attachment point. Basestation identification information 7160 includes information identifyingthe base station attachment point being used by WT 7200, e.g.,information identifying a base station, base station sector, and/orcarrier or tone block pair associated with the attachment point.Terminal identification information 7162 includes WT 7100 identificationinformation and base station assigned wireless terminal identifierstemporarily associated with WT 7100, e.g., a registered user identifier,an active user identifier, an ON state identifier associated with alogical DCCH channel tone. Timing information 7164 includes currenttiming information, e.g., identifying a current OFDM symbol time withina recurring timing structure. Timing information 7164 is used by fixedtype control module 7126 in conjunction with uplink timing/frequencystructure information 7178 and fixed type report transmission schedulinginformation 7184 in deciding when to transmit different types of fixedreports. Timing information 7164 is used by flexible report controlmodule 7128 in conjunction with uplink timing/frequency structureinformation 7178 and flexible type report transmission schedulinginformation 7186 in deciding when to transmit a flexible report. Amountof uplink data queued 7166, e.g., amounts of MAC frames in request groupqueues and/or combinations of amounts of MAC frames in request groupqueue sets, is used by report prioritization module 7136 in selectingthe type of report to be communicated in a flexible report slot. Signalinterference information 7168 is also used by prioritization module 7136in selecting the type of report to be communicated in a flexible reportslot. Report change information 7170, e.g., information indicatingdeltas from previously communicated DCCH reports, obtained from changedetermination module 7138 is used by report prioritization module 7136in selecting the type of report to be communicated in a flexible reportslot.

System data/information 7142 includes a plurality of sets of basestation data/information (BS 1 data/information 7172, . . . , BS Mdata/information 7174), DCCH report transmission scheduling information7182, fixed type report information 7188, and flexible type reportinformation 7190. BS 1 data/information 7172 includes downlink timingand frequency structure information 7176 and uplink timing/frequencystructure information 7178. Downlink timing/frequency structureinformation 7176 includes downlink carrier information, downlink toneblock information, number of downlink tones, downlink tone hoppinginformation, downlink channel segment information, OFDM symbol timinginformation, and grouping of OFDM symbols. Uplink timing/frequencystructure information 7178 includes uplink carrier information, uplinktone block information, number of uplink tones, uplink tone hoppinginformation, uplink channel segment information, OFDM symbol timinginformation, and grouping of OFDM symbols. The uplink timing/frequencystructure information 7178 includes tone hopping information 7180.

DCCH report transmission scheduling information 7182 is used incontrolling the transmission of reports to a base station, e.g., accessnode, using dedicated segments of a communications control channel. DCCHtransmission scheduling information 7182 includes informationidentifying the composite of different DCCH segments in a recurringreporting schedule identifying the location and type of fixed typereports within the recurring schedule and identifying the location offlexible type reports within the recurring schedule. Report transmissionscheduling information 7182 includes fixed type report information 7184and flexible type report information 7186. For example, in one exemplaryembodiment the recurring schedule includes 40 indexed DCCH segments, andthe composite of each indexed segment in terms of fixed and/or flexiblereport inclusion is identified by report transmission schedulinginformation 7182. FIG. 10 provides an example of exemplary DCCH reporttransmission schedule information corresponding to a recurring structureincluding 40 indexed DCCH segments used in a full-tone DCCH mode ofoperation occurring in a beaconslot. In the example, of FIG. 10, theBODY 4 reports are flexible reports and the TYPE2 reports are identifierreports identifying the type of report communicated in a correspondingBODY4 report for the same DCCH segment. The other illustrated reports,e.g., DLSNR5 report, ULRQST1 report, DLDNSNR3 report, ULRQST3 report,RSVD2 report, ULRQST4 report, ULTXBKF5 report, DLBNR4 report, RSVD1report, and DLSSNR4 report, are fixed type reports. There are more fixedreports than flexible reports in one iteration of the reportingschedule. In some embodiments, the reporting schedule includes at least8 times as many fixed reports as flexible reports in one iteration ofthe reporting schedule. In some embodiments, the reporting scheduleincludes, on average, less than one dedicated control channel segmentused to report a flexible report for each nine dedicated control channelsegments used to transmit a fixed report.

Fixed type report information 7188 includes information identifying theformat for each of the plurality of fixed types of reports communicatedover the dedicated control channel, e.g., number of information bitsassociated with a report and interpretation given to each of thepossible bit patterns that can be communicated. The plurality of fixedtype information reports include: uplink traffic channel requestreports, a wireless terminal self-nose report, e.g., a downlinksaturation level of self-noise SNR report, an absolute report ofdownlink SNR, a relative report of downlink SNR, an uplink transmissionpower report, e.g., a WT transmission power backoff report, and aninterference report, e.g., a beacon ratio report. FIGS. 13, 15, 16, 18,19, 26, 29, and 30 illustrate exemplary fixed type report information7188 corresponding to a DLSNR5 report, a DLDSNR3 report, a ULRQST1report, a ULRQST4 report, an ULRQST 3 report, an ULTxBKF5 report, and aDLBNR4 report, respectively.

Flexible type report information 7190 includes information identifyingthe format for each of the potential types of reports that may beselected to be communicated in a flexible report that is to communicatedover the dedicated control channel, e.g., number of information bitsassociated with a report and interpretation given to each of thepossible bit patterns that can be communicated. Flexible type reportinformation 7190 also includes information identifying a flexible typeindicator report to accompany the flexible report, e.g., number ofinformation bits associated with the flexible type indicator report anddesignation of the type of flexible report that each bit patternsignifies. In some embodiments, at least some of the types of reportsthat may be selected by the WT to be communicated in a flexible reportare the same as the fixed type of report. For example, in one exemplaryembodiment the flexible report can selected from a set of reportsincluding a 4 bit uplink traffic channel request report and a 4 bitdownlink saturation level of SNR report, the 4 bit uplink trafficchannel request report and the 4 bit downlink saturation level of SNRreport following the same format used when communicated as a fixed typereport in a predetermined fixed position in the recurring reportingschedule. FIGS. 31, 18, and 30 illustrate exemplary flexible type reportinformation 7190.

FIG. 72 is a drawing of an exemplary wireless terminal 7200, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary WT 7200 may be any of the wireless terminals of the exemplarysystem of FIG. 1. Exemplary WT 7200 may be any of the WTs (136, 138,144, 146, 152, 154, 168, 170, 172, 174, 176, 178) of exemplary system100 of FIG. 1. Exemplary wireless terminal 7200 includes a receivermodule 7202, a transmitter module 7204, a processor 7206, user I/Odevices 7208, and a memory 7210 coupled together via a bus 7212 overwhich the various elements may interchange data/information.

Memory 7210 includes routines 7218 and data/information 7220. Theprocessor 7206, e.g., a CPU, executes the routines 7218 and uses thedata/information 7220 in memory 7210 to control the operation of thewireless terminal 7200 and implement methods.

Receiver module 7202, e.g., an OFDM receiver, is coupled to receiveantenna 7203 via which the wireless terminal 7200 receives downlinksignals from base stations. Receiver module 7202 includes a decoder 7214which decodes at least some of the received downlink signals. Receiveddownlink signals include signals conveying base station attachment pointidentification information, e.g., beacon signals, and signals includingbase station assigned wireless terminal identifiers, e.g., an ON stateidentifier assigned to WT 7200 by a base station attachment point, theON state identifier associated with dedicated control channel segmentsto be used by WT 7200. Other received downlink signals includeassignment signals corresponding to uplink and/or downlink trafficchannel segments and downlink traffic channel segment signals.Assignments of uplink traffic channel segments by a base stationattachment point to WT 7200 may be in response to received backloginformation reports from WT 7200.

Transmitter module 7204, e.g., an OFDM transmitter, is coupled to atransmit antenna 7205 via which the wireless terminal 7200 transmitsuplink signals to base stations. Transmitter module 7204 is used fortransmitting at least some of the generated backlog information reports.The transmitted generated backlog information reports are transmitted bytransmitter module 7204 in uplink control channel segments dedicated tothe wireless terminal 7200. Transmitter module 7204 is also used fortransmitting uplink traffic channel segment signals. Transmitter module7204 includes an encoder 7216 which is used to encode at least some ofthe uplink signals prior to transmission. In some embodiments, eachindividual dedicated control channel uplink segment is encodedindependently of other dedicated control channel uplink segments. Invarious embodiments, the same antenna is used for both the transmitterand receiver.

User I/O devices 7208, e.g., microphone, keyboard, keypad, switches,camera, speaker, display, etc., are used to input/output user data,control applications, and control the operation of the wirelessterminal, e.g., allowing a user of WT 7200 to initiate a communicationssession.

Routines 7218 includes a communications routine 7222 and wirelessterminal control routines 7224. Communications routine 7222 performsvarious communications protocols used by wireless terminal 7200.Wireless terminal control routines 7224 controls operations of thewireless terminal 7200 including receiver module 7202 control,transmitter module 7204 control, and user I/O devices 7208 control.Wireless terminal control routines 7224 are used to implement methods.

Wireless terminal control routines 7224 include a queue statusmonitoring module 7226, a transmission backlog report generation module7228, a transmission backlog report control module 7230, and a codingmodule 7332. Queue status monitoring module 7266 monitors the amount ofinformation in at least one of a plurality of different queues used tostore information to be transmitted. The amount of information in aqueue changes over time, e.g., as additional data/information needs tobe transmitted, data/information is successfully transmitted,data/information needs to be retransmitted, data/information is dropped,e.g., due to a time consideration or due to the termination of a sessionor application. Transmission backlog report generation module 7288generates different bit size backlog information reports providingtransmission backlog information, e.g. 1 bit uplink request reports. 3bit uplink request reports, and 4 bit uplink request reports.Transmission backlog report control module 7230 controls thetransmission of generated backlog information reports. Transmissionbacklog report generation module 7228 includes an information groupingmodule 7234. Information grouping module 7234 groups status informationcorresponding to different sets of queues. Grouping module 7234 supportsdifferent information groupings for backlog information reports ofdifferent bit sizes. Coding module 7332 codes information to betransmitted in dedicated uplink control channel segments, and for atleast some segments, the coding module 7332 codes a transmission backlogreport with at least one additional backlog report used to communicatenon-backlog control information. Possible additional reports, which areencoded with transmission backlog reports for a DCCH segment, includesignal to noise ratio reports, self-noise report, an interferencereport, and a wireless terminal transmission power report.

Data/information 7220 includes user/device/session/resource information7236, system data/information 7238, queue information 7240, DCCH channelinformation 7242 including assigned logical tone information 7244, basestation identification information 7246, terminal identificationinformation 7248, timing information 7250, combined request groupinformation 7252, generated 1 bit uplink request report 7254, generated3 bit uplink request report 7256, generated 4 bit uplink request report7258, generated additional DCCH report 7260, and coded DCCH segmentinformation 7262.

User/device/session/resource information 7236 includes informationpertaining to communications sessions, e.g., peer node information,addressing information, routing information, state information, andresource information identifying uplink and downlink air link resources,e.g., segments, allocated to WT 7200. Queue information 7240 includesuser data that WT 7200 intends to transmit, e.g., MAC frames of userdata associated with a queue, and information identifying the amount ofuser data that WT 7200 intends to transmit, e.g., a total number of MACframes associated with a queue. Queue information 7240 includes requestgroup 0 information 7264, request group 1 information 7266, requestgroup 2 information 7268, and request group 3 information 7270.

DCCH channel information 7242 includes information identifying DCCHsegments allocated to WT 7200, e.g., information identifying a DCCH modeof operation, e.g., a full-tone DCCH mode or a split tone DCCH mode andinformation identifying an assigned logical DCCH tone 7244 in a DCCHchannel structure being used by the base station attachment point. Basestation identification information 7246 includes information identifyingthe base station attachment point being used by WT 7200, e.g.,information identifying a base station, base station sector, and/orcarrier or tone block pair associated with the attachment point.Terminal identification information 7248 includes WT 7200 identificationinformation and base station assigned wireless terminal identifierstemporarily associated with WT 7200, e.g., a registered user identifier,an active user identifier, an ON state identifier associated with alogical DCCH channel tone. Timing information 7250 includes currenttiming information, e.g., identifying a current OFDM symbol time withina recurring timing structure. Timing information 7250 is used bytransmission backlog report control module 7230 in conjunction withuplink timing/frequency structure information 7278 and storedtransmission backlog reporting schedule information 7281 in decidingwhen to transmit different types of backlog reports. Combined requestgroup information 7254 includes information pertaining to combinationsof request groups, e.g., a value identifying the amount of information,e.g., total number of MAC frames, to be transmitted corresponding to thecombination of request group 0 and request group 1.

Generated 1 bit uplink request report 7254 is a 1 information bittransmission backlog report generated by transmission backlog reportgeneration module 7228 using queue information 7240 and/or combinedrequest group information 7252, and 1 bit size report mappinginformation 7290. Generated 3 bit uplink request report 7256 is a 3information bit transmission backlog report generated by transmissionbacklog report generation module 7228 using queue information 7240and/or combined request group information 7252, and 3 bit size reportmapping information 7292. Generated 4 bit uplink request report 7258 isa 4 information bit transmission backlog report generated bytransmission backlog report generation module 7228 using queueinformation 7240 and/or combined request group information 7252, and 4bit size report mapping information 7294. Generated additional DCCHreport 7260 is, e.g., a generated downlink absolute SNR report, agenerated delta SNR report, a generated interference report, e.g., abeacon ratio report, a generated self-noise report, e.g., a WTself-noise report of saturation level of SNR, a WT power report, e.g., aWT transmission power backoff report. Coding module 7234 codes atransmission backlog report 7254, 7256, 7258, with a generatedadditional report 7260, for a given DCCH segment, obtaining coded DCCHsegment information. In this exemplary embodiment, each DCCH segment isthe same size, e.g., uses the same number of tone-symbols, regardless ofwhether the transmission backlog report included in the DCCH segment isa 1 bit report, 3 bit report, or 4 bit report. For example, for one DCCHsegment a 1 bit UL request transmission backlog report is jointly codedwith a 5 bit downlink absolute SNR report; for another DCCH segment a 3bit UL request transmission backlog report is jointly coded with a 3 bitdownlink delta SNR report; for another DCCH segment a 4 bit UL requesttransmission backlog report is jointly coded with a 2 bit reservedreport.

System data/information 7238 includes a plurality of sets of basestation information (BS 1 data/information 7272, . . . , BS Mdata/information 7274), dedicated control channel report transmissionreporting schedule information 7280, stored transmission backlog reportmapping information 7288, and queue sets' information 7296. BS1data/information 7272 includes downlink timing/frequency structureinformation 7276 and uplink timing/frequency structure information 7278.Downlink timing/frequency structure information 7276 includes downlinkcarrier information, downlink tone block information, number of downlinktones, downlink tone hopping information, downlink channel segmentinformation, OFDM symbol timing information, and grouping of OFDMsymbols. Uplink timing/frequency structure information 7278 includesuplink carrier information, uplink tone block information, number ofuplink tones, uplink tone hopping information, uplink channel segmentinformation, OFDM symbol timing information, and grouping of OFDMsymbols. DCCH report transmission reporting schedule information 7280includes stored transmission backlog reporting schedule information7281. FIG. 10 provides exemplary DCCH transmission schedule informationcorresponding to a recurring schedule of 40 indexed DCCH segments in abeaconslot for a full-tone DCCH mode of operation, the beaconslot beinga structure used in the timing/frequency structure of the base station.Stored transmission backlog reporting schedule information includesinformation identifying the location of each of transmission backlogreports, e.g., the location of the ULRQST1, ULRQST3, and ULRQST4 reportsin FIG. 10. The stored transmission backlog reporting schedulinginformation 7281 is used by the transmission backlog report controlmodule 7230 in determining when to transmit a report of a particular bitsize. The stored transmission backlog reporting schedule information7281 includes 1 bit size report information 7282, 3 bit size reportinformation 7284, and 4 bit size report information 7286. For example,with respect to FIG. 10, 1 bit size report information 7282 includesinformation identifying that an ULRQST1 report corresponds to the LSB ofDCCH segment with index s2=0; 3 bit size report information 7284includes information identifying that an ULRQST3 report corresponds tothe 3 LSBs of DCCH segment with index s2=2; 4 bit size reportinformation 7286 includes information identifying that an ULRQST4 reportcorresponds to the 4 LSBs of DCCH segment with index s2=4.

The stored transmission backlog scheduling information 7281 indicatesthat more 1 bit size backlog reports are to be transmitted than 3 bitsize backlog reports in one iteration of the transmission reportschedule. The stored transmission backlog scheduling information 7281also indicates that more or the same number of 3 bit size backlogreports are to be transmitted than 4 bit size backlog reports in oneiteration of the transmission report schedule. For example, in FIG. 10,there are 16 identified ULRQST1 reports, 12 identified ULRQST3 reports,and 9 identified ULRQST4 reports. In this exemplary embodimentcorresponding to FIG. 10, the flexible reports, Body 4 reports, mayconvey a 4 bit ULRQST report, and under a case where the 3 flexiblereports, of one iteration of the reporting structure, carry a ULRQST4report, the wireless terminal communicates 12 ULRQST4 reports.

Stored transmission backlog report mapping information 7288 includes 1bit size report information 7290, 3 bit size report information 7292,and 4 bit size report information 7294. Examples of 1 bit size reportmapping information 7290 includes FIG. 16 and FIG. 61. Examples of 3 bitsize report mapping information include FIGS. 19, 21, 23, 25, 64, 66,68, and 70. Examples of 4 bit size report mapping information includeFIGS. 18, 20, 22, 24, 63, 65, 67, and 69. Stored transmission backlogmapping information 7288 includes information indicating a mappingbetween queue status information and bit patterns that can becommunicated using the different bit size backlog reports. In thisexemplary embodiment, the 1 bit size backlog report provides backloginformation corresponding to a plurality of different transmissionqueues; the one bit indicates the existence of information to betransmitted or lack thereof corresponding to the combination of requestgroup 0 and request group 1. In various embodiments, the smallest bitsize, e.g., 1 bit size, backlog report is used for highest prioritytraffic, e.g., where the highest priority is voice or control traffic.In some embodiments, the second bit size report, e.g., the 3 bit sizereport, communicates a delta, with respect to a previously communicatedthird bit size report, e.g., 4 bit size report; FIGS. 63 and 64illustrates such a relationship. In some embodiments, the second fixedsize report, e.g., the 3 bit size report, provides information on twosets of queues. For example, consider FIG. 41, the second type of reportcommunicates information on a second set of queues and a third set ofqueues. In various embodiments, the third size report, e.g., the 4 bitsize report, provides information on one set of queues. In some suchembodiments, the one set of queues includes one request group queue, tworequest group queues, or three request group queues. In someembodiments, there are predetermined number of request groups for uplinktraffic, e.g., four, RG0, RG1, RG2, and RG3, and a third fixed sizereport, e.g., the four bit size report is capable of communicatingbacklog information corresponding to any of the different request groupqueues. For example, consider FIG. 41, a third type report communicatesinformation on one of a fourth set of queues, a fifth set of queues, asixth set of queues or a seventh set of queues, and for any givendictionary the third type of report is capable of communicatinginformation pertaining to RG0, RG1, RG2, and RG3.

Queue sets' information 7296 including information identifying groupingof queues to be used when generating transmission backlog reports. FIG.41 illustrates exemplary groupings of queues used in various exemplarytypes of transmission backlog reports.

FIG. 74 is a drawing of an exemplary wireless terminal 7400, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary wireless terminal 7400 may be any of the wireless terminals ofFIG. 1. Exemplary wireless terminal 7400 includes a receiver module7402, a transmitter module 7404, a processor 7406, user I/O devices7408, and memory 7410 coupled together via a bus 7412 over which thevarious elements interchange data and information.

Memory 7410 includes routines 7418 and data/information 7420. Theprocessor 7406, e.g., a CPU, executes the routines 7418 and uses thedata/information 7420 in memory 7410 to control the operation of thewireless terminal 7400 and implement methods. User I/O devices 7408,e.g., microphone, keyboard, keypad, switches, camera, display, speaker,etc., are used to input user data, output user data, allow a user tocontrol applications, and/or control various functions of the wirelessterminal, e.g., initiate a communications session.

Receiver module 7402, e.g., an OFDM receiver, is coupled to a receiveantenna 7403 via which the wireless terminal 7400 receives downlinksignals from base stations. Received downlink signals include, e.g.,beacon signals, pilot signals, downlink traffic channel signals, powercontrol signals including closed loop power control signals, timingcontrol signals, assignment signals, registration response signals, andsignals including base station assigned wireless terminal identifiers,e.g., an ON state identifier associated with a DCCH logical channeltone. Receiver module 7402 includes a decoder 7414 used to decode atleast some of the received downlink signals.

Transmitter module 7404, e.g., an OFDM transmitter, is coupled to atransmit antenna 7405 via which the wireless terminal 7400 transmitsuplink signals to base stations. In some embodiments, the same antennais used for receiver and transmitter, e.g., the antenna is coupledthrough a duplexer module to receiver module 7402 and transmitter module7404. Uplink signals include, e.g., registration request signals,dedicated control channel segment signals, e.g., conveying a referencesignal which can be measured by a base station and reports including WTpower reports such as a WT transmission power backoff report, and uplinktraffic channel segment signals. Transmitter module 7404 includes anencoder 7416 used to encode at least some of the uplink signals. DCCHsegments, in this embodiment, are encoded on a per segment basis.

Routines 7418 includes a communications routine 7422 and wirelessterminal control routines 7422. The communications routine 7422implements the various communications protocols used by the wirelessterminal 7400. Wireless terminal control routines 7422 include a reportgeneration module 7426, a wireless terminal transmission power controlmodule 7430, a dedicated control channel control module 7432, a tonehopping module 7434, and a report format control module 7436. Reportgeneration module 7426 includes a computation sub-module 7428.

Report generation module 7426 generates power reports, e.g., wirelessterminal transmission power backoff reports, each power reportindicating a ratio of a maximum transmit power of the wireless terminalto the transmit power of a reference signal having a power level knownto the wireless terminal at a point in time corresponding to the powerreport. Wireless terminal transmission power control module 7430 is usedfor controlling the wireless terminal's transmission power level basedon information including at least one closed loop power level controlsignal received from a base station. The closed loop power controlsignal received from the base station may be a signal used to controlthe wireless terminal transmitter power so that a desired received powerlevel is achieved at the base station. In some embodiments, the basestation does not have actual knowledge of the wireless terminals actualtransmission power level and/or maximum transmit power level. In somesystem implementations different devices may have different maximumtransmit power levels, e.g., a desk top wireless terminal may have adifferent maximum transmission power capability than a portable notebookcomputer implemented wireless terminal, e.g., operating off batterypower.

Wireless terminal transmission power control module 7430 performs closedloop power control adjustments of a transmission power level associatedwith the dedicated control channel. Dedicated control channel controlmodule 7432 determines which single logical tone in a plurality oflogical tones is to be used for the dedicated control channel signaling,said single logical tone being dedicated to the wireless terminal foruse in transmitting control signaling using a set of dedicated controlchannel segments.

Tone hopping module 7434 determines at different points in time a singlephysical OFDM tone to be used to communicate dedicated control channelinformation during a plurality of consecutive OFDM symbol transmissiontime intervals. For example, in one exemplary embodiments, a dedicatedcontrol channel segment corresponding to a single dedicated controlchannel logical tone includes 21 OFDM tone-symbol, the 21 OFDMtone-symbols comprising three sets of 7 OFDM tone-symbols, each set ofseven OFDM tone-symbols corresponding to a half-slot of sevenconsecutive OFDM symbol transmission time periods and corresponding to aphysical OFDM tone, each of the three sets may correspond to a differentphysical OFDM tone with the OFDM tone for a set being determined inaccordance with tone hopping information. Report format control module7436 controls the format of the power report as a function of which oneof a plurality of dedicated control channel modes of operation is beingused by the wireless terminal 7400 at the time the report istransmitted. For example, in one exemplary embodiment, the wirelessterminal uses a 5 bit format for the power report when in a full-toneDCCH mode of operation and uses a 4 bit power report when in asplit-tone mode of operation.

Computation sub-module 7428 subtracts a per-tone transmission power ofan uplink dedicated control channel in dBm from a maximum transmissionpower of the wireless terminal in dBm. In some embodiments, the maximumtransmission power is a set value, e.g., a predetermined value stored inthe wireless terminal or a value communicated to the wireless terminal,e.g., from a base station, and stored in the wireless terminal. In someembodiments, the maximum transmission power depends on a power outputcapacity of the wireless terminal. In some embodiments, the maximumtransmission power is dependent upon the type of wireless terminal. Insome embodiments, the maximum transmission power is dependent upon amode of operation of the wireless terminal, e.g., with different modescorresponding to at least two of the following: operation using anexternal power source, operation using a battery, operation using abattery having a first level of energy reserve, operation using abattery having a second level of energy reserve, operation using abattery with an expected amount of energy reserve to support a firstduration of operational time, operation using a battery with an expectedamount of energy reserve to support a second duration of operationaltime, operation in a normal power mode, operation in a power saving modesaid maximum transmit power in the power saving mode being lower thansaid maximum transmit power in said normal power mode. In variousembodiments, the maximum transmission power value is a value which hasbeen selected to be in compliance with a government regulation limitingthe maximum output power level of the wireless terminal, e.g., themaximum transmission power value is selected to be the maximumpermissible level. Different devices may have different maximum powerlevel capabilities which may or may not be known to a base station. Thebase station can, and in some embodiments does, use the backoff reportin determining the supportable uplink traffic channel data throughput,e.g., per transmission segment throughput, which can be supported by thewireless terminal. This is because the backoff report providesinformation about the additional power which can be used for trafficchannel transmissions even though the base station may not know theactual transmission power level being used or the maximum capability ofthe wireless terminal since the backoff report is provided in the formof a ratio.

In some embodiments the wireless terminal can support one or morewireless connections at the same time, each connection having acorresponding maximum transmission power level. The maximum transmissionpower levels, indicated by values, may be different for differentconnections. In addition, for a given connection the maximumtransmission power level may vary over time, e.g., as the number ofconnections being supported by the wireless terminal varies. Thus, itmay be noted that even if the base station knew the maximum transmissionpower capability of a wireless terminal, the base station may not beaware of the number of communications links being supported by thewireless terminal at a particular point in time. However, the backoffreport provides information which informs the base station about theavailable power for a given connection without requiring the basestation to know about other possible existing connections which may beconsuming power resources.

Data/information 7420 includes user/device/session/resource information7440, system data 7442, received power control signal information 7484,maximum transmission power information 7486, DCCH power information7490, timing information 7492, DCCH channel information 7494, basestation identification information 7498, terminal identificationinformation 7499, power report information 7495, additional DCCHreports' information 7493, coded DCCH segment information 7491, and DCCHmode information 7489. DCCH channel information 7494 includes assignedlogical tone information 7496, e.g., information identifying the singlelogical DCCH channel tone currently allocated to the wireless terminalby a base station attachment point.

User/device/session/resource information 7440 includes useridentification information, username information, user securityinformation, device identification information, device type information,device control parameters, session information such as peer nodeinformation, security information, state information, peer nodeidentification information, peer node addressing information, routinginformation, air link resource information such as uplink and/ordownlink channel segments assigned to WT 7400. Received power controlinformation 7484 includes received WT power control commands from a basestation, e.g., to increase, decrease or do not change the transmissionpower level of the wireless terminal with respect to a control channelbeing closed loop power controlled, e.g., a DCCH channel. Maximumtransmit power information 7486 includes a maximum wireless terminaltransmit power value to be used in generating a power report. Referencesignal information 7496 includes information identifying the referencesignal to be used in the power report calculation, e.g., as the DCCHchannel signal, and a transmit power level of the reference signal at apoint in time, the point in time being determined based on the starttransmit time of the DCCH segment in which the power report iscommunicated and power report time offset information 7472. DCCH powerinformation 7490 is the result of computation sub-module 7428 which themaximum transmit power information 7486 and the reference signal info7497 as input. DCCH power information 7490 is represented by a bitpattern in power report information 7495 for communicating a powerreport. Additional DCCH reports' information 7493 includes informationcorresponding to other types of DCCH reports, e.g., other DCCH reportssuch as a 1 bit uplink traffic channel request report or a 4 bit uplinktraffic channel request report, which is communicated in the same DCCHsegment as a power report. Coded DCCH segment information 7491 includesinformation representing a coded DCCH segment, e.g., a DCCH segmentconveying a power report and an additional report. Timing information7492 includes information identifying the timing of the reference signalinformation and information identifying the timing of the start of aDCCH segment to be used to communicate a power report. Timinginformation 7492 includes information identifying the current timing,e.g., relating indexed OFDM symbol timing within an uplink timing andfrequency structure to recurring DCCH reporting schedule information,e.g., to indexed DCCH segments. Timing information 7492 is also used bythe tone hopping module 7344 to determine tone hopping. Base stationidentification information 7498 includes information identifying thebase station, base station sector, and/or base station tone blockassociated with a base station attachment point being used by thewireless terminal. Terminal identification information 7499 includeswireless terminal identification information including base stationassigned wireless terminal identifiers, e.g., a base station assignedwireless terminal ON state identifier to be associated with DCCH channelsegments. DCCH channel information 7496 includes information identifyingthe DCCH channel, e.g., as a full-tone channel or as one of a pluralityof split tone channel. Assigned logical tone information 7496 includesinformation identifying the logical DCCH tone to be used by the WT 7400for its DCCH channel, e.g., one DCCH logical tone from the set of tonesidentified by information 7454, the identified tone corresponding to abase station assigned WT ON state identifier of terminal ID information7499. DCCH mode information 7489 includes information identifying thecurrent DCCH mode of operation, e.g., as a full-tone format mode ofoperation or a split-tone format mode of operation. In some embodiments,DCCH mode information 7489 also includes information identifyingdifferent mode of operation corresponding to different values for themaximum transmit power information, e.g., a normal mode and a powersaving mode.

System data/information 7442 includes a plurality of sets of basestation data/information (BS 1 data/information 7444, BS Mdata/information 7446), DCCH transmission reporting schedule information7462, power report time offset information 7472 and DCCH report formatinformation 7476. BS 1 data/information 7442 includes downlinktiming/frequency structure information 7448 and uplink timing/frequencystructure information 7450. Downlink timing/frequency structureinformation 7448 includes information identifying downlink tone sets,e.g., a tone block of 113 tones, downlink channel segment structure,downlink tone hopping information, downlink carrier frequencyinformation, and downlink timing information including OFDM symboltiming information and grouping of OFDM symbols, as well as timinginformation relating the downlink and uplink. Uplink timing/frequencystructure information 7450 includes uplink logical tone set information7452, tone hopping information 7456, timing structure information 7458,and carrier information 7460. Uplink logical tone set information 7452,e.g., information corresponding to a set of 113 uplink logical tones inan uplink channel structure being used by a base station attachmentpoint, includes DCCH logical channel tone information 7454, e.g.,information corresponding to a subset of 31 logical tones used for thededicated control channel with a wireless terminal in the ON state usingthe BS 1 attachment point receiving one of the 31 tones to use for itsdedicated control channel segment signaling. Carrier information 7460includes information identifying the uplink carrier frequencycorresponding to a base station 1 attachment point.

DCCH transmission reporting schedule information 7462 includes DCCH fulltone mode recurring reporting schedule information 7464 and split-tonemode recurring reporting schedule information 7466. Full tone moderecurring reporting schedule information 7464 includes power reportschedule information 7468. Split tone mode recurring reporting scheduleinformation 7466 includes power report schedule information 7470. DCCHreport format information 7476 includes power report format information7478. Power report format information 7478 includes full-tone modeinformation 7480 and split tone mode information 7482.

DCCH transmission reporting scheduling information 7462 is used incontrolling the transmission of generated DCCH reports. Full tone moderecurring reporting scheduling information 7464 is in for controllingDCCH reports when the wireless terminal 7400 is operating in a full-tonemode of DCCH operation. Drawing 1099 of FIG. 10 illustrates exemplaryfull-tone mode DCCCH recurring reporting schedule information 7464.Exemplary power report schedule information 7468 is informationindicating that segment 1006 with index s2=6 and segment 1026 with indexs2=26 are each used to convey a 5 bit wireless terminal uplinktransmission power backoff report (ULTXBKF5). Drawing 3299 of FIG. 32illustrates exemplary split-tone mode DCCCH recurring reporting scheduleinformation 7466. Exemplary power report schedule information 7470 isinformation indicating that segment 3203 with index s2=3 and segment3221 with index s2=21 are each used to convey a 4 bit wireless terminaluplink transmission power backoff report (ULTXBKF4).

DCCH report format information 7476 indicates formats used for each ofthe DCCH reports, e.g., number of bits in a report, and the informationassociated with each of potential bit patterns that can be communicatedwith the report. Exemplary full-tone mode power report formatinformation 7480 includes information corresponding to Table 2600 ofFIG. 26 illustrating the format of ULTxBKF5. Exemplary split-tone modepower report format information 7482 includes information correspondingto Table 3500 of FIG. 35 illustrating the format of ULTxBKF4. BackoffReports ULTxBKF5 and ULTxBKF4 indicate a dB value.

Power report time offset information 7472 includes informationindicating a time offset between the point in time to which a generatedpower report corresponds, e.g., provides information for, and a start ofa communications segment in which said report is to be transmitted. Forexample, consider that a ULTxBKF5 report is to be communicated in anexemplary uplink segment corresponding to segment 1006 with index s2=6of a beaconslot and consider that the reference signal used ingenerating the report is the dedicated control channel signal, powerreport time offset information 7472. In such a case, the time offsetinformation 7472 includes information indicating a time offset betweenthe time to which the report information corresponds, e.g., the OFDMsymbol transmission time interval prior to the transmission time of thereport corresponding to the reference signal, e.g., DCCH signal,transmission power level and a start of the segment 1006 transmission.

FIG. 75 is a drawing 7500 used to explain features of an exemplaryembodiment using a wireless terminal transmission power report. Verticalaxis 7502 represents the transmission power level of the wirelessterminal's dedicated control channel, e.g., a single tone channel, whilehorizontal axis represents time 7504. The dedicated control channel isused by the wireless terminal to communicate various uplink controlinformation reports via dedicated control channel segment signals. Thevarious uplink control information reports include a wireless terminaltransmission power report, e.g., a WT transmission power backoff report,and other addition control information reports, e.g., uplink trafficchannel request reports, interference reports, SNR reports, self-noisereports, etc.

Each small shaded circle, e.g., circle 7506, is used to represent thetransmission power level of the dedicated control channel at acorresponding point in time. For example, each point in time, in someembodiments, corresponds to an OFDM symbol transmission time intervaland the identified power level is the power level associated with themodulation symbol corresponding to the single tone of the WT's DCCHchannel during that OFDM symbol transmission time interval. In someembodiments, each point in time, corresponds to a dwell, e.g.,representing a fixed number, e.g., seven, of consecutive OFDM symboltransmission time periods using the same physical tone for the wirelessterminal's DCCH channel.

Dashed line box 7514 represents a DCCH segment which conveys a WTtransmission power backoff report. The segment includes multiple OFDMsymbol transmission time periods. In some embodiments, a DCCH segmentincludes 21 OFDM tone-symbols and includes 21 OFDM symbol transmissiontime intervals, one OFDM tone-symbol corresponding to each of the 21OFDM symbol transmission time intervals.

The exemplary transmission backoff report indicates a ratio of a maximumtransmission power of the WT, e.g., a set value, to the transmit powerof a reference signal. In this exemplary embodiment, the referencesignal is the DCCH channel signal at a point in time which is offsetfrom the start of the DCCH segment used to communicate the transmissionpower backoff report. Time 7516 identifies the start of the DCCH segmentconveying the WT transmission power backoff report. Time offset 7518,e.g., a predetermined value, relates time 7516 to time 7512 which is thetransmission time of the reference signal used to generate the powerreport of segment 7514. X 7508 identifies the reference signal in termsof a power level 7510 and the time 7512.

In addition to the DCCH control channel which is used in variousembodiments for wireless terminals in an ON state, it should beappreciated that the system also supports additional dedicated uplinkcontrol signaling channels, e.g., timing control channels and/or statetransition request channels which may be dedicated to a wirelessterminal. These additional channels may exist in the case of the holdstate in addition to the ON state with terminals in the ON-State beingprovided the DCCH control channel in addition to the timing and statetransition request channels. Signaling on the timing control and/orstate transition request channels occurs at a much lower rate thansignaling on the DCCH control channel, e.g., at rate ⅕ or less from thewireless terminals perspective. In some embodiments, the dedicateduplink channels provided in the hold state based on Active user IDsassigned by the base station attachment point while DCCH channelresources are allocated by the base station attachment point based oninformation including an ON state identifier assigned by the basestation attachment point.

FIG. 76 is a flowchart 7600 of an exemplary method of operating awireless terminal, e.g., mobile node, to report transmission backloginformation. For example, the wireless terminal, in some embodiments,maintains one or more request group queues corresponding to uplinkinformation that the wireless terminal would like to communicate to abase station via uplink traffic channel segments; and the wirelessterminal reports transmission backlog information corresponding to therequest group queue(s) as part of uplink reports in a dedicated controlchannel reporting structure.

Operation of the exemplary method starts in step 7602 and proceeds tostep 7604 or 7606. Step 7604 is a step performed in some embodiments,but omitted in other embodiments. In step 7604, the wireless terminalstores reporting control factor mapping information, e.g., informationmapping at least one of an interference report and a transmission powerreport to at least one reporting control factor as a function of storedvalues. For example, in one exemplary embodiment, the information beingstored in step 7604 may include information defining the conditionalequations of table 6200 of FIG. 62, the interference report is a beaconratio report, the transmission power report is a transmission powerbackoff report, and the stored values include conditional limit values,e.g., the values to which x and b are compared in column 6202 of table6200 of FIG. 62. The storing of step 7604, is in some embodimentsperformed as part of an initial load, e.g., factory load, of thewireless terminal, and/or as part of an update in the field. Operationproceeds from step 7604 to step 7606.

In step 7606, the wireless terminal generates at least one reportingcontrol factor as a function of at least one of: channel qualityinformation, available transmission power information, device capabilityinformation, and quality of service information. For example, in oneembodiment, the wireless terminal generates y and z control factors inaccordance with table 6200. Operation proceeds from step 7606 to step7608.

In step 7608, the wireless terminal maps a number of frames to becommunicated to a report value as a function of said generated at leastone reporting control factor. For example, in one exemplary embodiment,the wireless terminal uses the generated y and z control factors fromtable 6200 in determining a report value for a request report, e.g., areport value for a 4 bit uplink request report of one of table 6300 ofFIG. 63, table 6500 of FIG. 65, table 6700 of FIG. 67 and table 6900 ofFIG. 69. The selection of the one of table 6300, table 6500, table 6700,and table 6900 to use, in mapping the number of frames to becommunicated to a report value for the 4 bit uplink request report isdependent upon the request dictionary currently in use by the wirelessterminal.

In some embodiments, the reporting control factor is a function ofchannel quality information and the channel quality information includesat least one of: uplink interference information, downlink interferenceinformation, uplink signal to noise information, downlink signal tonoise information, uplink signal to interference information anddownlink signal to interference information.

In some embodiments the reporting control factor is a function ofchannel quality information and the channel quality information includesuplink interference information. For example in some exemplaryembodiments, the uplink interference information includes beacon ratioinformation. For example, control factors y of table 6200 is a functionof input value b, an adjusted generic beacon ratio report, which is afunction of the most recent generic 4 bit downlink beacon ratio reportDLBNR4. Control factors z of table 6200 is also a function of inputvalue b, an adjusted generic beacon ratio report, which is a function ofthe most recent generic 4 bit downlink beacon ratio report DLBNR4.

In some embodiments the reporting control factor is a function ofavailable transmission power information and the available transmissionpower information includes information indicating the amount oftransmission power available for transmission of information includingat least said frames. For example in some exemplary embodiments, theavailable transmission power information includes transmission powerbackoff report information. For example, control factors y of table 6200is a function of input value x, the most recent 5 bit uplinktransmission power backoff report (ULTXBKF5). Control factors z of table6200 is also a function of input value x, the most recent 5 bit uplinktransmission power backoff report (ULTXBKF5).

In various embodiments, the reporting control factor is also function ofanother factor, said another factor being received from a base station,e.g., via a broadcast channel signal. For example, in some exemplaryembodiments, the another factor is an interference report gainadjustment value. For example, in an exemplary embodiment using table6200 of FIG. 62 to determine control factors y and z, the interferencereport adjust gain factor is the value of an uplink traffic channel rateflash assignment offset value (ulTCHrateFlashAssignmentOffset), wherethe base station sector broadcasts the ulTCHrateFlashAssignmentOffset ina downlink broadcast channel. The wireless terminal uses a receivedulTCHrateFlashAssignment value to determine the adjusted generic beaconratio report value, b, in accordance withb=b₀−ulTCHrateFlashAssignmentOffset, where − is defined in the dB senseand where b₀ is the most recent generic beacon ratio report value. Insome embodiments, the wireless terminal usesulTCHrateFlashAssignmentOffset equal to 0 dB until the wireless terminalreceives the value from the broadcast channel.

In some embodiments, the reporting control factor is a function of themaximum number of frames of information that can be communicated in asegment. In some such embodiments, the maximum number of frames ofinformation that can be communicated in a segment is a function of thehighest rate option that the wireless terminal can support. For example,in table 6200 of FIG. 62, control factor z is a function of N_(max), thenumber of MAC frames that fit in a segment at the highest rate optionthat the wireless terminal can support R_(max), where there is apredetermined N_(max) value for each R_(max) value. Refer to column 6206of table 6200. At different times, e.g., due to different channelconditions, the wireless terminal may support different maximum rates,and this affects the determination of the control factor z.

In various embodiments generating a reporting control factor includesdetermining an expected rate of transmission. In some such embodiments,the mapping includes quantizing differently depending on the rate oftransmission. For example, the expected rate of transmission, in someembodiments, is the maximum rate of possible transmission, and thequantization of a request report is performed differently depending upondifferent expected transmission rates. For example, the quantization isdifferent in request report tables 6300, 6500, 6700, and 6900 as afunction of control parameter z, which is dependent upon the value ofR_(max).

In some embodiments, mapping a number of frames to be communicated to areport value as a function of said generated at least one reportingcontrol factor includes selecting a reporting control factor type, e.g.,y or z, as a function of an amount of backlog. For example, considerthat the wireless terminal is using the request dictionary (RD referencenumber=1) with the format for ULRQST4 of table 6500 of FIG. 65, and thewireless terminal wants to report backlog information pertaining to thecombination of request groups 1 and 3, e.g., N[1]+N[3] information, thewireless terminal use a first reporting control factor type, e.g.reporting control factor y, for lower levels of backlog and a secondreporting control factor type z, for higher levels of backlog. In someembodiments, mapping a number of frames to be communicated to a reportvalue as a function of said generated at least one reporting controlfactor includes: selecting a reporting control factor type to use as afunction of the type of information the wireless terminal wants tocommunicate. For example, in some embodiments, a wireless terminal mayuse a first reporting control factor type, e.g., reporting controlfactor y, when reporting backlog information pertaining to a firstrequest group or set of request groups, e.g., request group 1information, N[1], and a second reporting control factor type, e.g.,reporting control factor z, when reporting backlog informationpertaining to a second request group or set of request groups, e.g., thecombination of request group 2 and 3, N[2]+N[3].

In some embodiments, the method further comprises step 7610, in whichthe wireless terminal maps another number of frames to be communicatedto another report value, said mapping another number of frames includingselecting not to apply a reporting control factor. In some suchembodiments, selecting not to apply a reporting control factor isperformed as a function of at least one of the type of information to bereported, e.g., request group or set of request groups, and the amountof backlog. For example, consider that the wireless terminal is usingthe request dictionary (RD reference number=1) with the format forULRQST4 of table 6500 of FIG. 65, and the wireless terminal wants toreport request group 2 backlog information, e.g., N[2] information, thewireless terminal does not use a reporting control factor, e.g., thewireless terminal does not use a value for reporting control factor y orz in determining the report value.

FIG. 77 comprising the combination of FIG. 77A, FIG. 77B and FIG. 77C isa drawing of a flowchart 7700 of an exemplary method of operating awireless terminal, e.g., mobile node, to report transmission backloginformation. The exemplary method starts in step 7702 and proceeds, insome embodiments, to step 7704 and/or step 7708. In step 7704, thewireless terminal stores reporting control factor mapping information,e.g., information mapping at least one of an interference report, e.g.,a beacon ratio report, and a transmission power report, e.g., atransmission power backoff report, to at least one reporting controlfactor as a function of stored values resulting in mapping informationfor control factors 7706. For example, mapping information for controlfactors 7706, in is one exemplary embodiment, information represented bytable 6200 of FIG. 62 which is used to determine reporting controlfactors y and z, and stored values include limit values used in thecondition column 6202.

In step 7708, the wireless terminal stores transmission backlog reportdictionary information (report dictionary 1 information 7710, . . . ,report dictionary N information 7712, wherein at least one of thereports defined by at least one dictionary uses reporting controlfactors. For example, consider an exemplary embodiment using four reportdictionaries represented by FIGS. 63, 64, 65, 66, 67, 68, 69 and 70; thefour bit uplink request report (ULRQST4) for each dictionary usesreporting control factors y and z.

Steps 7704 and/or 7708 are, in some embodiments performed as part of aninitialization process for the wireless terminal, e.g., a factory load.Steps 7704 and/or 7708 are, in some embodiments, performed as part of anupgrade, e.g., an in-field upgrade as new request dictionaries becomeavailable. In some embodiments, mapping information for control factors7706 and/or report dictionary information, e.g., one or more of (reportdictionary 1 information 7710, . . . , report dictionary N information7712) is preprogrammed in the wireless terminal, e.g., as part ofsoftware, hardware, and/or firmware, and the wireless terminal does notperform storing operations of steps 7704 and/or 7708.

Operation proceeds from step 7702 to steps 7714, 7720, 7726, 7732, 7738,and via connecting node A 7742 to step 7744. In step 7714, the wirelessterminal maintains transmission backlog information, e.g., updating oneor more request group queues (request group 1 queue backlog information7716, . . . , request group N queue backlog information 7718), on anongoing basis. For example, a number of uplink MAC frames of trafficchannel information to be communicated in a particular request group areincreased as more user data, e.g., input data, to be communicated viathe uplink corresponding to the request group occurs; as frames of userdata corresponding to a request group are successfully communicated, thenumber of uplink frames may be decremented accordingly; as a timeoutexpires the number of uplink frames may be decremented accordingly.

In step 7720, the wireless terminal determines wireless terminaltransmission power levels, and then in step 7722 the wireless terminalgenerates transmission power reports, e.g., a transmission power backoffreport, resulting in stored transmission power report information 7724.Steps 7720 and 7724 are performed on an ongoing basis.

In step 7726, the wireless terminal measures channel conditions, e.g.,measuring received downlink broadcast signals such as pilot and/orbeacon signals from one or more base station attachment points.Operation proceeds from step 7726 to step 7728, where the wirelessterminal generates interference reports. For example, the wirelessterminal generates a beacon ratio report using measurements from step7726 corresponding to a serving base station sector transmitter and oneor more other base station transmitters and using loading factorinformation. From the operation of step 7728 interference reportinformation 7730 is determined, e.g., a generic beacon ratio reportvalue, which is stored.

In step 7732, the wireless terminal monitors for a gain adjustmentfactor, e.g., a gain adjustment factor corresponding to the currentserving base station attachment point, which is broadcast via abroadcast channel signal. Operation proceeds from step 7732 to step7734, where the wireless terminal receives and stores the gainadjustment factor 7736. For example, in one exemplary embodiment, thegain adjustment factor is referred to as an uplink traffic channel rateflash assignment offset (ulTCHrateFlashAssignmentOffset) value. In someembodiments, if the gain adjustment value is not received, a defaultvalue, e.g., 0 dB, is used for the gain adjustment value.

In step 7738, the wireless terminal identifies a report dictionary touse resulting in current report dictionary identification information7740. Step 7738 is performed on an ongoing basis. In some embodiments,one of the reporting dictionaries is a default dictionary, and thereport dictionary may be, and sometimes is, changed to a differentreport dictionary during ongoing operations, e.g., to better facilitatewireless terminal current reporting needs.

In step 7744, the wireless terminal determines whether the wirelessterminal is to transmit an uplink transmission backlog report as afunction of a reporting control factor. Current report dictionaryidentification information 7740 and report dictionary information(report dictionary 1 information 7710, . . . , report dictionary Ninformation 7712) are used as input to step 7712. In some embodiments,some transmission backlog reports use reporting control factors whileother transmission backlog reports do not use reporting control factors.For example 1 bit uplink request reports or 3 bit uplink request reportsmay not use reporting control factors while 4 bit uplink request reportsmay use reporting control factors. In some embodiments, some reportdictionaries use reporting control factors while other reportdictionaries do not use reporting control factors. Operations of step7744 are performed by the wireless terminal on an ongoing basis.

For each report to be communicated by the wireless terminal which is touse a reporting control factor, the wireless terminal proceeds to step7746. In step 7746, the wireless terminal generates at least onereporting control factor as a function of at least one of channelquality information, available transmission power information, devicecapability information, and quality of service information. Step 7746includes sub-steps 7748, 7752, 7754, 7758, and 7762.

In sub-step 7748, the wireless terminal determines an adjustedinterference report value 7750 using said interference reportinformation 7730 and gain adjustment factor 7736. For example, consideran embodiment using the implementation of FIG. 62, the interferencereport information 7730 is the most recent generic beacon ratio reportvalue b₀, the adjusted interference report value 7750 is the value ofvariable b, the gain adjustment factor 7736 is the received value ofbroadcast channel variable ulTCHrateFlashAssignmentOffset, whereb=b₀−ulTCHrateFlashAssignmentOffset, and where “−” is in the dB sense.

Operation proceeds from sub-step 7748 to sub-step 7752. In step 7752 thewireless terminal determines a 1^(st) reporting control factor as afunction of interference information and power information. In step7752, the wireless terminal uses mapping information for control factors7706, transmission report power information 7724, and adjustedinterference report information 7750 to determine a 1^(st) controlfactor value 7764. For example, consider an embodiment using FIG. 62information, the mapping information for control factors 7706 includesthe 1^(st) column 6202 and the second column 6204, the transmissionpower report information 7724 is the value of the most recenttransmission power backoff report referred to as the x value, theadjusted interference report value is the adjusted beacon ratio reportvalue referred to as b value, and the 1^(st) control factor 7764 is thedetermined y value from column 6204 which satisfies the input conditionsconsidered.

Operation proceeds from step 7752 to step 7754, where the wirelessterminal determines a highest rate option supported by the wirelessterminal, e.g., a highest rate option currently supported by thewireless terminal, referred to as R_(max) 7756. Operation proceeds fromstep 7754 to step 7758, where the wireless terminal uses the determinedhighest rate option R_(max) to determined a number of frames, e.g.,number of MAC frames, corresponding to the determined highest rateoption for a segment, e.g., an uplink traffic channel segment. Thedetermination of step 7758 is referred to as N_(max).

Operation proceeds from step 7758 to step 7762. In step 7762, thewireless terminal determines a second reporting control factor as afunction of interference information, power information, and the highestrate supported by the wireless terminal. In step 7762, the wirelessterminal uses mapping information for control factors 7706, transmissionreport power information 7724, adjusted interference report information7750, and maximum number of frames information 7760 to determine a2^(nd) control factor value 7766. For example, consider an embodimentusing FIG. 62 information, the mapping information for control factors7706 includes the 1^(st) column 6202 and the third column 6206, thetransmission power report information 7724 is the value of the mostrecent transmission power backoff report referred to as the x value, theadjusted interference report value is the adjusted beacon ratio reportvalue referred to as b value, and the 2^(nd) control factor 7766 is thedetermined z value from column 6206 which satisfies the input conditionsconsidered.

Operation proceeds from step 7746 via connecting node B 7768 to step7770. In step 7770, the wireless terminal maps a number of frames to becommunicated to a report value as a function of said generated at leastone reporting control factor. Step 7770 uses as input current reportdictionary identification information 7740, report dictionaryinformation 1 7710, . . . , report dictionary N information 7712, 1^(st)control factor value 7764, 2^(nd) control factor value 7766, and requestgroup queue backlog information (request group 1 queue backloginformation 7716, . . . , request group N backlog information 7718). Forexample, consider that the wireless terminal is currently using requestdictionary with reference number=2 using the reporting format of FIG. 67for 4 bit uplink request reports, that y=2, that the wireless terminalhas a backlog of 4 frames in the request group with index number=2 suchthat N[2]=4, that the wireless terminal has a backlog of 2 frames in therequest group with index number=3 such that N[3]=2; ceil(N[2]+N[3])/y=ceil (6/2)=3. Therefore in step 7770 the report value isset to the 4 bit pattern of 0b0111.

Operation proceeds from step 7770 to step 7772, where the wirelessterminal transmits a transmission backlog report, e.g., a 4 bit uplinktransmission backlog report, including said report value from step 7770,to a base station. For example, the backlog report with the report valueof step 7770 is in some embodiments communicated via a dedicated controlchannel segment. In some embodiments, the backlog report is communicatedwith another report in the same segment.

FIG. 78 is a drawing of an exemplary wireless terminal 7800, e.g.,mobile node, implemented in accordance with various embodiments.Exemplary wireless terminal 7800 includes a receiver module 7802, atransmitter module 7804, a processor 7806, user I/O devices 7808, and amemory 7810 coupled together via a bus 7812 over which the variouselements may interchange data and information. Memory 7810 includesroutines 7818 and data/information 7820. The processor 7806, e.g., aCPU, executes the routines 7818 and uses the data/information 7820 inmemory 7810 to control the operation of the wireless terminal andimplement methods.

The receiver module 7802, e.g., an OFDM receiver, is coupled to receiveantenna 7803 via which the wireless terminal receives downlink signalsfrom base stations. Downlink signals include, e.g.,timing/synchronization signals such as beacon and pilot signals,registration signals, state transition signals, power control commandsignals, loading factor information signals, broadcast signals includinggain adjustment signals, assignment signals and downlink traffic channelsignals. Receiver module 7802 includes a decoder 7814 for decoding atleast some of the received downlink signals.

The transmitter module 7804, e.g., an OFDM transmitter, is coupled totransmit antenna 7805, via which the wireless terminal transmits uplinksignals to base stations. In some embodiments, the same antenna is usedfor transmitter and receiver. Transmitter module 7804 includes anencoder 7816 for encoding at least some of the uplink signals. Uplinksignals include, e.g., registration request signals, dedicated controlchannel signals including uplink transmission backlog request reportsignals, interference reports, and power reports, and uplink trafficchannel segment signals.

Routines 7818 include a communications routine 7822 and wirelessterminal control routines 7824. The communications routine 7822implements various communications protocols used by the wirelessterminal. Wireless terminal control routines 7824 include a 1^(st)control factor generation module 7826, a 2^(nd) control factorgeneration module 7828, a mapping module 7830, a channel qualitydetermination module 7832, a transmission power information generationmodule 7834, a maximum transmission rate determination module 7836, andan expected transmission rate determination module 7840.

1^(ST) control factor generation module 7826 generates a first controlfactor 7870 as a function of at least one of channel qualityinformation, available transmission power information, device capabilityinformation and quality of service information. 2^(nd) control factorgeneration module 7828 generates a second control factor 7872 as afunction of at least one of channel quality information, availabletransmission power information, device capability information andquality of service information. For example, in one exemplaryembodiment, the first reporting control factor 7870 is the value ofvariable z in table 6200 of FIG. 62 and, the 1^(st) control factorgeneration module 7826 uses the information of column 6202 and 6206 ofTable 6200, beacon ratio report information, transmission power backoffreport information and maximum rate information to determine the valuefor reporting control factor z. Continuing with the example, the secondreporting control factor 7872 is the value of variable y in table 6200of FIG. 62 and, the 2^(nd) control factor generation module 7828 usesthe information of column 6202 and 6204 of Table 6200, beacon ratioreport information and transmission power backoff report information todetermine the value for reporting control factor y.

Mapping module 7830 maps a number of frames, e.g., MAC frames, to becommunicated to a report value as a function of at least one reportingcontrol factor. Thus mapping module 7830 maps request group queueinformation, e.g., at least some of (request group 1 number of frames7880, . . . , request group N number of frames 7882), to a requestreport determined value, in accordance with the request dictionarycurrently in use by the wireless terminal. Mapping module 7830 usesrequest dictionary information 7844 corresponding to the dictionary inuse and at least one of 1^(st) reporting control factor 7870 and 2^(nd)reporting control factor 7872 to perform the mapping and determine therequest report value 7884 to be communicated to the base station. In oneexemplary embodiment, the request report is a 4 bit uplink requestreport (ULRQST4), the wireless terminal supports 4 different requestdictionaries represented by FIGS. 63, 65, 67 and 69, the wirelessterminal supports four uplink request groups having numbers of frames tobe communicated N[0], N[1], N[2], N[3], respectively, and the controlfactors are represented by the values of variables y and z determined inaccordance with FIG. 62. Thus mapping module 7830, for a given ULRQST4report uses one of the request dictionaries, the wireless terminal andbase station both being aware of the reporting dictionary being used bythe wireless terminal for the report.

Channel quality determination module 7832 generates informationincluding at least one of: uplink interference information 7854,downlink interference information 7858, uplink signal to noiseinformation 7860 and downlink signal to noise information 7862. At leastone of reporting control factor 7870 and/or reporting control factor7872 determined by module 7826 and module 7828, respectively, is afunction of channel quality information 7852 generated by the channelquality determination module 7832. In some embodiments, both reportingcontrol factors 7870, 7872 are a function of channel quality information7852.

Transmission power information generation module 7834 generatesavailable transmission power information 7864, e.g., a wireless terminaltransmission power backoff report value. At least one of reportingcontrol factor 7870 and/or reporting control factor 7872 determined bymodule 7826 and module 7828, respectively, is a function of availabletransmission power information 7864 generated by module 7834. In someembodiments, both reporting control factors 7870, 7872 are a function ofavailable transmission power information 7864.

Maximum transmission rate determination module 7836 determines a currenthighest rate option supported by the wireless terminal (information7874), e.g., for an uplink traffic channel segment. At least one ofreporting control factor 7870 and/or reporting control factor 7872determined by module 7826 and module 7828, respectively, is a functionof a maximum number of frames of information that can be communicated ina segment 7876 given the current highest rate option 7874 determined tobe supported by the wireless terminal.

Expected rate transmission module 7840 determines the expected rate oftransmission 7878, e.g., for one or more uplink traffic channel segment.In some embodiments generating at least one of a reporting controlfactor and a request report value is determined as a function of anexpected rate of transmission. Thus, in some such embodiment thedetermined expected rate of transmission is used by at least one ofmodules 7826, 7828 and 7830.

Data/information 7820 includes mapping information for reporting controlfactors 7842, request dictionary information 7844, channel qualityinformation 7852, available transmission power information 7864, devicecapability information 7866, quality of service information 7868, a1^(st) reporting control factor 7870, a 2^(nd) reporting control factor7872, a maximum transmission rate currently supported 7874, a currentmaximum number of frames/segment 7876, an expected rate of transmission7878, request group 1 number of frames 7880, . . . , request group Nnumber of frames 7882, and request report determined value 7884.

Mapping information for reporting control factors 7842 in one embodimentincludes information of table 6200 of FIG. 62.

Request dictionary information 7884 includes one or more sets of requestdictionary information (request dictionary 1 information 7846, . . . ,request dictionary n information 7848). Request dictionary 1 information7846 includes mapping information for request report 7850. In oneexemplary embodiment request dictionary information 7844 includesinformation of table 6300 of FIG. 63, table 6500 of FIG. 65, table 6700of FIG. 67 and table 6900 of FIG. 69. For example mapping informationfor request report 7850 may correspond to table 6300 of FIG. 63.

Channel quality information 7852 includes uplink interferenceinformation 7854, downlink interference information 7858, uplink signalto noise information 7860, and downlink signal to noise information7862. Uplink interference information 7854 includes beacon ratioinformation 7856. Beacon ratio information 7856 includes beacon ratioreport information, e.g., an uplink interference report value derivedfrom beacon signals, pilot channel signals, and/or loading factorinformation, and an adjusted beacon ratio report value, the adjustmentbeing as a function of a received broadcast gain adjustment signal.

Available transmission power information 7864, e.g., a wireless terminaltransmission power backoff report value, is an output of module 7834 andused by at least one of control factor generation modules 7826, 7828.

Device capability information 7866 includes, e.g., uplink powercapability information, supported uplink rate option information, typesof input or inputs, e.g., voice, text, and/or image, bufferingcapability information, programs support information, concurrent sessioncapability information, receiver strength information, transmitterstrength information, frequency band capability information, number oftransmitters, etc. Quality of service information 7868 includes, e.g.,current estimated quality of service information, current measuredquality of service information, and user subscription tier level ofservice.

1^(st) reporting control factor 7870 and 2^(nd) reporting controlfactors 7872 are outputs of module 7826, 7828, respectively and used asinput by mapping module 7830 in determining a request report value. Theuse of reporting control factors greatly expands the reportingpossibilities for a given fixed size report, e.g., a four bit report, ofa given reporting dictionary, thus facilitating a wide range ofreporting possibilities and a wide range of different quantizationschemes. Thus the small size, e.g., 4 bit report, using control factorsas input, can favorably accommodate a wide range of reportingpossibilities.

Maximum rate currently supported 7874 identifying a maximum uplink rateoption that the wireless terminal can currently accommodate is an outputof maximum rate determination module 7836. In some exemplaryembodiments, a determined current maximum rate option corresponds to acurrent maximum number of frames/segment 7876, e.g., MAC frames peruplink traffic channel segment, which is used by at least one of controlfactor generation modules 7826, 7828. Expected rate of transmission 7878is an output of module 7840.

Request group 1 number of frames 7880, . . . , request group N number offrames 7882 indicate uplink transmission backlog informationcorresponding to different request group queues, e.g., counts of MACframes awaiting to be transmitted for each of the request group queues.Request report determined value 7884 is an output of mapping module7830, e.g., a 4 bit pattern to be communicated in a 4 bit uplink requestreport (ULRQST4 report).

FIG. 79 comprising the combination of FIG. 79A and FIG. 79B is aflowchart 7900 of an exemplary method of operating a base station inaccordance with various embodiments. The exemplary method starts in step7902, where the base station is powered on and initialized. Operationproceeds from step 7902 to step 7904. In step 7904, the base stationbroadcasts a value, e.g., a gain adjustment factor, to be used bywireless terminals in determining at least some reporting controlfactors. For example, in one exemplary embodiment, the gain adjustmentfactor, e.g., an uplink traffic channel rate flash assignment offsetvalue, is broadcast as part of a broadcast channel in a recurringstructure and is intended to adjust the value of the beacon ratioreport.

Operation proceeds from step 7904 to step 7906. In step 7906, the basestation receives an uplink interference report, e.g., a beacon ratioreport, from a wireless terminal. Operation proceeds from step 7906 tostep 7908. In step 7908, the base station receives a transmission powerreport, e.g., a wireless terminal transmission power backoff report,from said wireless terminal. Operation proceeds from step 7908 to step7910. In step 7910, the base station receives a transmission backlogreport from said wireless terminal, e.g., a four bit uplink requestreport, said transmission backlog report communicating a report value,e.g. a multi-bit report value. For example, in an exemplary embodimentwhere the transmission backlog report is a four bit uplink requestreport (ULRQST4) the report value may be one of 16 possibilities. Insome embodiments, each of received interference report, transmissionpower report and transmission backlog report from the wireless terminalare received over the same dedicated control channel allocated to thewireless terminal, e.g., each report being conveyed in differentdedicated control channel segments but using the same logical dedicatedcontrol channel tone.

Operation proceeds from step 7910 to step 7912. In step 7912, the basestation determines a reporting control factor or factors correspondingto said received transmission backlog report, said reporting controlfactor being a function of at least one of channel quality information,wireless terminal available transmission power information, wirelessterminal device capability information and quality of serviceinformation. In some embodiments, the channel quality informationincludes at least one of uplink interference information, downlinkinterference information, uplink signal to noise information, downlinksignal to noise information, uplink signal to interference information,and downlink signal to interference information. In step 7912, the basestation is attempting to determine the same reporting control factor,e.g., type of reporting control factor and value for the reportingcontrol factor, that was used by the wireless terminal in generating thetransmission backlog report which was received and is being processed.In one exemplary embodiment, the base station uses the information oftable 6200 of FIG. 62 to determine the value for at least one of controlfactors y and z given the inputs derived from the received uplinkinterference report of step 7906 and the received transmission powerreport of step 7908.

In some embodiments, determining a reporting control factor in step 7912includes determining a reporting control factor type from among aplurality of reporting control factor types as a function of a bitpattern of at least a portion of the received report value. For example,consider that the base station has implemented 4 bit uplink requestdictionary mapping of table 6500 of FIG. 65, and that the report valueis one of 0101, 0110, 0111, 1000, then report control factor type y isused. Alternatively, if the report value is one of 1001, 1010, 1011,1100, 1101, 1110 and 1111, then reporting control factor type z is used.In some embodiment, the format for a report of a dictionary may bepartitioned such that the type of reporting control factor being usedcan be determined by considering the value of a portion of the bits ofthe report value, e.g., half of the possible report values maycorrespond to use of a first type of report value, e.g., y, and a secondhalf of the possible report values may correspond to use of a secondtype of report value, e.g., z, and one bit, e.g., the most significantbit of the report value can be used to determine the type of reportingcontrol factor.

In some embodiments, step 7912 includes sub-step 7914. In sub-step 7914,the base station estimates the maximum number of frames of informationthat the wireless terminal will be able to communicate in a segment ifsaid segment is allocated to said wireless terminal. For example,consider that the base station uses information of Table 6200 of FIG.62, if the base station is attempting to determine the value of controlfactor z, the base station calculates a value for N_(max), and uses thatvalue in determining reporting control factor z. Alternatively, if thebase station needs to determine the value of control factor y, but notz, then step 7914 is skipped.

Operation proceeds from step 7912 to step 7916. In step 7916, the basestation interprets said received report value as a function of saiddetermined reporting control factor. For example, in some exemplaryembodiments, the base station determines the reporting dictionary in useby the wireless terminal, and then using the determined reportdictionary mapping information and determined reporting control factorthe base station interprets the report value, e.g., the report valuerepresented by a pattern of 4 bits. In one exemplary embodiment, thebase station uses the report dictionary mapping information of one oftable 6300 of FIG. 63, table 65 of FIG. 65, table 6700 of FIG. 67, andtable 6900 of FIG. 69 and reporting control factor value correspondingto one of reporting control parameter y or z to interpret a 4 bit bitpattern of the 4 bit uplink request report.

Step 7916 includes step 7918. In step 7918, the base station determinesbacklog information of frames to be transmitted by said wirelessterminal. For example, consider an embodiment using the reportdictionaries of FIGS. 63, 65, 67, and 69; in that embodiment informationabout four request group queues is represented by frame countinformation N[0], N[1], N[2], and N[3], which is recovered from aninterpretation of the report value.

Operation proceeds from step 7916 via connecting node A 7920 to step7922. In step 7922, the base station receives a second transmissionbacklog report from said wireless terminal, said second transmissionbacklog report communicating a second report value, said secondtransmission backlog report being of the same type as said transmissionbacklog report, e.g., both reports are 4 bit uplink request reports(ULRQST4) reports in a recurring dedicated control channel structure.

Then, in step 7924, the base station determines a reporting controlfactor corresponding to said second received report, said reportingcontrol factor corresponding to said second received report being afunction of at least one of channel quality information, wirelessterminal available transmission power information, wireless terminaldevice capability information and quality of service information. Then,in step 7926, the base station interprets said received second reportvalue as a function of said determined second reporting control factor.Step 7926 includes step 7928 in which the base station determinesbacklog information of frames to be transmitted by said wirelessterminal.

In some embodiments, wherein the first and second reporting values arethe same but wherein control factor values are different, interpretingsaid received second reporting value determines different backloginformation of frames to be transmitted by said wireless terminal thaninterpreting said received first report value. For example, considerthat the base station has implemented control factor mapping of table6200 of FIG. 62 and 4 bit uplink request dictionary mapping of table6500 of FIG. 65. Further consider that the wireless terminal hastransmitted another one of at least one of uplink interference reportand transmission power report prior to step 7922 resulting in adifferent value for reporting control factor (y) corresponding to firstand second ULRQST4 reports and that the first and second receivedULRQST4 reports (of steps 7910 and 7922) respectively, have communicatedthe same bit pattern 0101. In one case where reporting control factory=1, the base station interprets the bit pattern as communicating thatceil((N[1]+N[3])/1)=1; therefore N[1]+N[3]=1. In the other case wherereporting control factor y=2, the base station interprets the bitpattern as communicating that ceil((N[1]+N[3])/2)=1; thereforeN[1]+N[3]=2 or N[1]+N[3]=1.

Now consider that the reporting control factor variable was z of FIG.62, reporting control parameter z can, at any given time for a wirelessterminal has one of ten different values (1, 2, 3, 4, 5, 6, 7, 8, 9, 10)as a function of a beacon ratio report value, a transmission powerbackoff report value, and a maximum number of frames (Nmax). Thus for agiven bit pattern for a given reporting dictionary, e.g., bit pattern1001 of reporting dictionary of FIG. 65, ten different interpretationsare possible.

It should be appreciated that the use of reporting control factors canvastly increase the reporting possibilities and possible quantizationschemes available for such a small number of bits in a report, e.g., afour bit report with respect to a fixed reporting scheme. It should alsobe appreciated that the beacon ratio report and transmission powerbackoff report utilized by the wireless terminal and base station, areimplemented and utilized for purposes other than generating a reportingcontrol factor, thus those reports do not represent additional overheadsignaling, but can be conveniently used to enhance backlog reportingpossibilities.

In some embodiments, steps 7930, 7932 and 7934 are performed. Operationproceeds from step 7926 to step 7930. In step 7930, the base stationreceives a third transmission backlog report from said wirelessterminal, said third transmission backlog report communicating a thirdreport value, said third transmission backlog report being of the sametype as said transmission backlog report, e.g., an ULRQST4 report.Operation proceeds from step 7930 to step 7932. In step 7932, the basestation determines to interpret said received third report value withoutusing a reporting control factor, said decision to interpret withoutusing a reporting control factor being performed as a function of a bitpattern of a least a portion of said received third report value. Forexample, consider that the base station has implemented 4 bit uplinkrequest dictionary mapping of table 6500 of FIG. 65, and that the thirdreport value is one of 0000, 0001, 0010, 0011 and 0100. In such asituation, the base station does not use a reporting control factor,e.g., y or z value, to interpret the report. The base station, in someembodiments, determines that a reporting control factor is not used bychecking the bit pattern of the report value. In some embodiments, theuse or non-use of a reporting control factor is intentionallypartitioned such that the use or non-use of a reporting control factorcan be determined by examining some but not all of the bits of thereport, e.g., half of the possible report values for an exemplary reportof an exemplary dictionary may correspond to non-use of a reportingcontrol factor and half of the possible report value may correspond touse of a reporting control factor. In some such exemplary embodiments,the base station by examining the value of one bit of the report value,e.g., the most significant bit, can determine whether or not a reportingcontrol factor is being used. Operation proceeds from step 7932 to step7934. In step 7934, the base station interprets said received thirdreport value without using a reporting control factor, e.g., saidinterpreting including determining backlog information of frames to betransmitted by said wireless terminal.

FIG. 80 comprising the combination of FIG. 80A, FIG. 80B and FIG. 80C isa flowchart 8000 of an exemplary method of operating a base station inaccordance with various embodiments. Operation of the exemplary methodstarts in step 8002, where the base station is powered on andinitialized and proceeds to steps 8004, 8008, 8014, 8020, and 8026.

In step 8004, the base station broadcasts a value, e.g., a gainadjustment value, to be used by wireless terminal in determining atleast some reporting control factors. Step 8006 uses gain adjustmentfactor information 8006 as input. For example, in one exemplaryembodiment the gain adjustment factor is referred to as an uplinktraffic channel rate flash assignment offset(ulTCHrateFlashAssignmentOffset) value and is broadcast as one of aplurality of different variables in a broadcast channel in a recurringtiming/frequency channel structure used by the base station. Step 8004is performed on an ongoing basis.

In step 8008, the base station maintains, on an ongoing basis, reportdictionary usage information (current report dictionary identificationinformation for WT 1 8010, . . . , current report dictionaryidentification information for WT N 8012). In one exemplary embodiment,the base stations supports four different reporting dictionariesincluding a default reporting dictionary, and at any given time awireless terminal using an attachment point of the base station uses oneof the four dictionaries, the wireless terminal and base station bothhaving knowledge of the report dictionary in use corresponding to anuplink backlog report being communicated.

In step 8014, the base station receives, on an ongoing basis, uplinkinterference reports, e.g., beacon ratio reports, from wirelessterminals. Step 8014 results in received interference reportinformation, e.g., beacon ratio report information, (interference reportinformation for wireless terminal 1 8016, . . . , interference reportinformation for wireless terminal N 8018.

In step 8020, the base station receives, on an ongoing basis,transmission power reports, e.g., wireless terminal transmission powerbackoff reports, from wireless terminals. Step 8020 results in receivedpower report information (power report information for wireless terminal1 8022, . . . , power report information for wireless terminal N 8024).

In step 8026, the wireless terminal receives, on an ongoing basis,transmission backlog reports, e.g., 4 bit uplink request reports(ULRQST4) from wireless terminals. Step 8026 results in received backlogreport values (backlog report value for WT 1 8028, . . . , backlogreport value for WT N 8030). For each received backlog report value tobe interpreted operation proceeds from step 8026 via connecting node A8032 to step 8034.

In step 8034, the base station determines a reporting control factor orfactors corresponding to a received transmission backlog report, saidreport control factor being a function of at least one of channelquality information, wireless terminal available transmission power,wireless terminal device capability information and quality of serviceinformation. Step 8034 includes sub-steps 8036, 8040, 8050 and 8052.

In sub-step 8036, the base station adjusts the received interferenceinformation, interference report information for WT i 8035 using gainadjustment factor information 8006 and obtains adjusted interferencereport information for WT i 8038. For example, input information WT i8035 is one of (interference report information for WT 1 8016, . . . ,interference report information 8018), where the value of i matches theindex of the WT which transmitted the backlog report being interpretedto which the control factors being determined correspond.

Operation proceeds from sub-step 8036 to sub-step 8040. In sub-step8040, the base station estimates the maximum number of frames ofinformation that WT i will be able to communicate in a segment, e.g., anuplink traffic channel segment, if the segment is allocated to WT i.Sub-step 8040 includes sub-step 8042 and 8046. In sub-step 8042, thebase station determines an expected maximum rate option, R_(max) 8044,and in step 8046, the base station uses the determined maximum rateoption to determine a number of frames, N_(max) 8048, corresponding tothe R_(max).

Operation proceeds from sub-step 8040 to sub-step 8050. In sub-step8050, the base station determines a 1^(st) reporting control factor, y8051, as a function of interference report information and power reportinformation. The power report information used as input in sub-step 8050is power report information for WT i 8049 which is one of (power reportinformation for WT 1 8022, . . . , power report information for WT N8024), where the value of i matches the index of the WT whichtransmitted the backlog report being interpreted to which the controlfactors being determined correspond. The interference report informationused as input in sub-step 8050 is adjusted interference reportinformation for WT i 8038. In one exemplary embodiment, the firstcontrol factor value y is determined in accordance with first column6202 and second column 6204 of table 6200 of FIG. 62. For example, thevalue of y 8051 can be either 1 or 2.

Operation proceeds from sub-step 8050 to sub-step 8052. In sub-step8052, the base station determines a 2^(nd) reporting control factor, z8053, as a function of interference report information, power reportinformation and rate information. The power report information used asinput in sub-step 8052 is power report information for WT i 8049 whichis one of (power report information for WT 1 8022, . . . , power reportinformation for WT N 8024), where the value of i matches the index ofthe WT which transmitted the backlog report being interpreted to whichthe control factors being determined correspond. The interference reportinformation used as input in sub-step 8050 is adjusted interferencereport information for WT i 8038. N_(max) 8048 which is based on rateinformation is also used as input to sub-step 8052. In one exemplaryembodiment, the second control factor value z is determined inaccordance with first column 6202 and third column 6206 of table 6200 ofFIG. 62. For example, the value of z 8053 can be one of the set {1, 2,3, 4, 5, 6, 7, 8, 9, 10}.

Operation proceeds from step 8034 via connecting node B 8054 to step8056. In step 8056, the base station interprets the received reportvalue as a function of determined reporting control factor(s). Step 8056includes sub-step 8058 and 8062. In sub-step 8058, the base stationidentifies the report dictionary information to use for interpretation.The base station includes one or more sets of report dictionaryinformation (report dictionary 1 information 8064, . . . , reportdictionary N information 8066) from which the base station selects basedon the value of current report dictionary identification information forWT i 8068. Current report dictionary information for WT i 8068 is theone of (current report dictionary ID for WT 1 8010, . . . , currentreport dictionary ID for WT N 8012), where the value of i the value ofthe wireless terminal index from which the backlog report beingprocessed corresponds. The output of step 8058 is identified reportdictionary information 8060. For example in one exemplary embodiment inwhich the base station supports four report dictionaries, information8060 corresponds to one of table 6300 of FIG. 63, table 6500 of FIG. 65,table 6700 of FIG. 67 and table 6900 of FIG. 69.

Operation proceeds from sub-step 8058 to sub-step 8062. In sub-step8062, the base station determines backlog information of frames to betransmitted by WT i. Sub-step 8062 uses as input: backlog report valuefor WT i 8070, reporting control factor y value 8051, reporting controlfactor z value 8053, and identified report dictionary information 8060.Backlog report value for WT i 8070 is one of (received backlog reportvalue for WT 1 8028, . . . , received backlog report value for WT N8030), where the value of i is the value of the wireless terminal indexfrom which the backlog report being processed corresponds. Determinedbacklog information, e.g., corresponding to one or more request groups,8063 is output from step 8063. For example, consider that the identifiedreport dictionary information 8060 corresponds to table 6500 of FIG. 65,backlog report value 8070 is the 4 bit pattern 0111, y=2 and z=7. Insuch a case the determined backlog information is: ceil ((N[1]+N[3])/2=3or, in other wireless the combination of request group 1 and requestgroup 3 has a backlog of 5 or 6 frames, e.g., MAC frames, tocommunicate. Alternatively, consider that the identified reportdictionary information 8060 corresponds to table 6500 of FIG. 65,backlog report value 8070 is the 4 bit pattern 0111, y=1 and z=4. Insuch a case the determined backlog information is: ceil ((N[1]+N[3])/1=3or, in other wireless the combination of request group 1 and requestgroup 3 has a backlog of 3 frames, e.g., MAC frames, to communicate.Alternatively, consider that the identified report dictionaryinformation 8060 corresponds to table 6500 of FIG. 65, backlog reportvalue 8070 is the 4 bit pattern 1101, y=2 and z=6. In such a case thedetermined backlog information is: ceil ((N[1]+N[3])/6=6 or, in otherwireless the combination of request group 1 and request group 3 has abacklog of 36 or 35 or 34 or 33 or 32 or 31 frames, e.g., MAC frames, tocommunicate. Alternatively, consider that the identified reportdictionary information 8060 corresponds to table 6500 of FIG. 65,backlog report value 8070 is the 4 bit pattern 1101, y=1 and z=4. Insuch a case the determined backlog information is: ceil ((N[1]+N[3])/4=6or, in other wireless the combination of request group 1 and requestgroup 3 has a backlog of 24 or 23 or 22 or 21 or 20 or 19 frames, e.g.,MAC frames, to communicate. Thus, as may be observed, the use of controlfactors allows multiple interpretations of a 4 bit uplink request reportcorresponding to the same request dictionary and facilitates variationsin quantization schemes.

FIG. 81 is a drawing of an exemplary base station 8100 implemented inaccordance with various embodiments. Exemplary base station 8100includes a receiver module 8102, a transmitter module 8104, a processor8106, an I/O interface 8108, and a memory 8110 coupled together via abus 8112 via which the various elements interchange data andinformation. Memory 8110 includes routines 8118 and data/information8120. The processor 8106, e.g., a CPU, executes the routines 8118 anduses the data/information 8120 in memory 8110 to control the operationof the base station 8100 and implement methods.

Receiver module 8102, e.g., an OFDM receiver, is coupled to receiveantenna 8103 via which the base station receives uplink signals fromwireless terminals, e.g., from wireless terminal 7800. Receiver module8102 includes a decoder 8114 for decoding at least some of the receiveduplink signals. Received uplink signals include registration signals,dedicated control channel signals, timing control signals, and uplinktraffic channel signals. The dedicated control channel signals includetransmission backlog reports such as a 4 bit uplink request report(ULRQST4), interference reports such as beacon ratio reports andtransmission power reports such as a wireless terminal transmissionpower backoff report.

Transmitter module 8104, e.g., an OFDM transmitter, is coupled totransmit antenna 8105 via which the base station 8100 transmits downlinksignals to wireless terminals. Transmitter module 8104 includes anencoder 8116 for encoding at least some of the transmitted downlinksignals. Downlink signals include timing/synchronization signals,registration signals, assignment signals, downlink traffic channelsignals and broadcast channel signals. The broadcast channel signalsinclude a parameter used by wireless terminals in determining areporting control factor, e.g., a gain adjustment parameter. Forexample, in one exemplary embodiment the gain adjustment parameter,referred to as a ulTCHrateFlashAssignmentOffset parameter value, is usedby wireless terminals in scaling a beacon ratio report value to obtainan adjusted beacon ratio report value, the adjusted beacon ratio reportvalue used an input in determining a reporting control factor.

I/O interface 8108 couples the base station 8100 to other network nodes,e.g., other base stations, routers, AAA nodes, home agent nodes, etc.and/or the Internet. Thus I/O interface 8108, by coupling base station8100 to a backhaul network, allows a wireless terminal using anattachment point of base station 8100 to participate in a communicationssession with a peer node using an attachment point of a different basestation.

Routines 8118 include a communications routine 8122 and base stationcontrol routines 8124. The communications routines 8122 implementvarious communications protocols used by the base station 8100. The basestation control routines 8124 include a scheduler module 8126, areporting control factor determination module 8128, a reportinterpretation module 8130, an interference report recovery module 8132,a wireless terminal transmission power report recovery module 8134, awireless terminal rate determination module 8136, a broadcast controlmodule 8138 and a report dictionary module 8140.

Scheduler module 8126 schedules air link resources to wireless terminalsusing an attachment point of base station 8100 in accordance with ascheduling policy. The air link resources include downlink and uplinktraffic channel segments. The scheduler module 8126 uses informationderived from received transmission backlog reports in deciding whichuplink traffic channel segments are assigned to which wirelessterminals.

Reporting control factor determination module 8128 determines values ofreporting control factors, a reporting control factor being a functionof at least one of channel quality information, wireless terminalavailable power information, wireless terminal device capabilityinformation and quality of service information. In some embodiments,wherein said reporting control factor determination module 8128determines said reporting control factor as a function of channelquality information, the channel quality information includes at leastone of uplink interference information, downlink interferenceinformation, uplink signal to noise information, downlink signal tonoise information, uplink signal to interference information, anddownlink signal to interference information. Reporting control factordetermination module 8128 includes a 1^(st) control factor sub-module8142 and a second control factor sub-module 8144. 1st reporting controlfactor sub-module 8142 determines values of 1^(st) reporting controlfactors, e.g., determined 1^(st) control factor 8176 for WT 1. 2ndreporting control factor sub-module 8144 determines values of 2^(nd)reporting control factors, e.g., determined 2^(nd) control factor 8178for WT 1. For example, in one exemplary embodiment the two reportingcontrol factors are y and z of table 6200 of FIG. 62 and reportingcontrol factor determination module 8128 determines values for y and zfor a wireless terminal from which it is receiving transmission backlogreports, e.g., ULRQST4 reports, in accordance with table 6200.

Report interpretation module 8130 determines backlog informationrelating to frames to be communicated by a wireless terminal whichtransmitted a received backlog report. For example, for WT 1,corresponding to received transmission backlog report 8150 the basestation obtains a report value 8168, e.g., an integer value in the rangeof 0 . . . 15 corresponding to a 4 bit pattern of a received ULRQST4report from WT1, and interprets the report as a function of determinedcontrol factors, e.g., y and/or z reporting control factor values, todetermine interpreted transmission backlog report information 8156. Invarious embodiments, the base station 8100 supports a plurality ofdifferent reporting dictionaries and the report interpretation module8130 uses the current dictionary for the WT to interpret a report. Forexample, in one exemplary embodiment, the base station 8100 supports 4report dictionaries for ULRQST4 report interpretation represented by theinformation of table 6300 of FIG. 63, table 6500 of FIG. 65, table 6700of FIG. 67 and table 6900 of FIG. 69. The base station reportinterpretation module 8130 using the appropriate one of the requestdictionaries, determined report control factors, and an input reportvalue, determines information pertaining to request group queues framecount information. For example, consider that the request dictionary ifthe one of table 6500, the report value=0110, and control factor y=2,the report interpretation module determines that ceil((N[1]+N[3])/y)=2,or in other words the combination of request group 1 and request group3, for the wireless terminal, has 3 or 4 MAC frames in backlog to betransmitted.

Interference report recovery module 8132, e.g., a beacon ratio reportrecovery module, recovers interference reports and interference reportinformation from wireless terminals, e.g., interference report 8152 fromWT 1 and corresponding interference report information 8170, e.g., abeacon ratio report value. Interference report information 8170 is usedas an input by the control factor determination module 8128, e.g., theinterference report information 8170 is the value of the variable b_(o)with reference to table 6200 of FIG. 62, the value b₀ is adjusted by again adjustment sub-module within reporting control factor determinationmodule 8128 using gain adjustment factor 8190, and the value of b isobtained which is used in determining reporting control factors y and z.

Wireless terminal transmission power report recovery module 8134recovers transmission power reports, e.g., transmission power backoffreports, from WTs and determines power report information, e.g. wirelessterminal transmission power availability information. For examplecorresponding to WT 1, recovery module 8134 recovers report 8154 andobtains power report information 8174. The power report information 8174is used as an input by the control factor determination module 8128,e.g., the power report information is the value of the variable x intable 6200 of FIG. 62.

Broadcast control module 8138 controls the broadcast of broadcastcommunications channel parameters including a gain adjustment factor8190. The gain adjustment factor parameter value 8190, e.g., the valueof the ulTCHrateFlashAssignmentOffset parameter described with respectto FIG. 62, is used by wireless terminals in determining reportingcontrol factors. The base station 8100 is aware of the broadcast gainadjustment parameter, and the reporting control factor determinationmodule 8128 also uses the gain adjustment factor 8190 in determiningcorresponding control factors, e.g., an adjusted interference reportvalue 8172 is obtained from an interference report value 8170.

Wireless terminal rate determination module 8136 determines rate optionscorresponding to wireless terminals, e.g., a maximum rate option thatthe wireless terminal is to use for an uplink traffic channel segment.In some embodiments, the rate determination module 8136 also determinesa maximum number of frames, e.g., MAC frames, corresponding to thedetermined rate option. In some embodiments, a separate module is usedfor determining a maximum number of frames information. In the exemplaryembodiment, at least some of the reporting control factors determined bymodule 8128 are determined as a function of current maximum rate optioninformation for a wireless terminal. For example, in one exemplaryembodiment the maximum frame information, e.g., an N_(max) value,derived from a determined current maximum rate option, e.g., a R_(max)value, for a wireless terminal is used by reporting control factordetermination module 8128 for determining the value of reporting controlfactor parameter z of table 6200 of FIG. 62.

Report dictionary module 8140 maintains current report dictionaryidentification information 8146, e.g., WT 1 current request dictionaryidentification information, corresponding to wireless terminals using abase station 8100 attachment point. Thus module 8140 tracks the currentreport dictionary in use by a wireless terminal such that the basestation can use the appropriate request dictionary when reportinterpretation module 8130 interprets a transmission backlog reportvalue.

Data/information 8120 includes a plurality of sets of wireless terminaldata/information (WT 1 data/information 8145, . . . , WT Ndata/information 8147), a plurality of reporting dictionary information(request dictionary 1 information 8184, . . . , request dictionary Ninformation 8186), report control factor mapping information 8188, and again adjustment factor 8190. In one exemplary embodiment the basestation 8100 supports 4 request dictionaries, and the report dictionaryinformation includes the information of tables 6300 of FIG. 63, table6500 of FIG. 65, table 6700 of FIG. 67 and table 6900 of FIG. 69. Reportcontrol mapping information 8188 includes, e.g., information included intable 6200 of FIG. 62 used to derive reporting control factors y and z.Gain adjustment factor 8190, e.g., a parameter such as aulTCHrateFlashAssignmentOffset parameter, used by both WTs and BS 8100in determining a reporting control factor, is broadcast under control ofbroadcast control module 8140 via transmitter module 8104 over abroadcast communications channel.

WT 1 data/information 8145 includes current request dictionaryidentification information 8146, received reports 8148, interpretedtransmission backlog report information 8156, a plurality of requestgroup frame information (request group 0 frame information 8158, . . . ,request group N frame information 8160), device capability information8162, quality of service information 8164, other quality information8166, report value 8168, interference report information 8170, adjustedinterference report information 8172, power report information 8174, adetermined 1^(st) control factor 8176, a determined 2^(nd) controlfactor 8178, maximum rate information 8180, and maximum number of framesinformation 8182.

Received reports 8148 includes transmission backlog report 8150,interference report 8152, and wireless terminal transmission powerreport 8154. In one exemplary embodiment the transmission backlog reportis a 4 bit uplink traffic request report (ULRQST4), the interferencereport is a 4 bit downlink beacon ratio report (DLBNR4), and thewireless terminal power report is a 5 bit uplink transmit backoff report(ULTxBKF5) or a 4 bit uplink transmit backoff report (ULTxBKF4). Reportvalue 8168, e.g., an integer value or bit pattern conveyed by theinformation bits or bits of the report such as the four bit pattern0110, corresponds to received transmission backlog report 8150.Interference report information 8170, e.g., a value in dB obtained fromreceived interference report 8152, is, e.g., one of the values of table2900 of FIG. 29 in the range of −3 db to 26 db.

Adjusted interference report information 8172, represents thecombination of the interference report information 8170 value and thegain adjustment factor 8190 value. Power report information 8174 isobtained from received wireless terminal transmission power report,e.g., a value of an ULTxBKF5 report of table 2600 of FIG. 26 in therange of 6.5 db to 40 dBs.

Determined 1^(st) control factor 8176 is an output of 1^(st) controlfactor sub-module 8142 while determined 2^(nd) control factor 8178 is anoutput of 2^(nd) control factor sub-module 8144. In one exemplaryembodiment the two reporting control factors are represented by thevariables y and z of table 6200 of FIG. 62.

Interpreted transmission backlog report information 8156 is an output ofreport interpretation module 8130, e.g., counts of MAC frames ofinformation to be transmitted in uplink traffic channel segments by WT 1corresponding to one or more request groups. Request group 0 frameinformation 8158 includes the base station's estimate of the number offrames corresponding to request group 0 in backlog for WT 1; requestgroup N frame information 8160 includes the base station's estimate ofthe number of frames corresponding to request group N in backlog for WT1. Request group frame information (8158, . . . , 8160) is updated basedupon interpreted transmission backlog report information 8156.

Device capability information 8162 includes, e.g., uplink powercapability information, supported uplink rate option information, typesof input or inputs, e.g., voice, text, and/or image, bufferingcapability information, programs support information, concurrent sessioncapability information, receiver strength information, transmitterstrength information, frequency band capability information, number oftransmitters, etc. Quality of service information 8164 includes, e.g.,current estimated quality of service information, current measuredquality of service information, and user subscription tier level ofservice. Other quality information 8166 includes downlink interferenceinformation, uplink signal to noise information, downlink signal tonoise information, uplink signal to interference information, anddownlink signal to interference information.

WT 1 data/information 8145 also includes information identifyingsegments, e.g., uplink traffic channel segments assigned by the basestation's scheduler 8126 to WT 1. In addition data/information 8145 alsoincludes user data, e.g., voice, audio, image, text, and/or file data,received and/or transmitted via traffic channel segments assigned to WT1, e.g., MAC frames of user data from WT 1 intended for a peer node ofWT 1, received via uplink traffic channel segments assigned to WT1.

The techniques of various embodiments may be implemented using software,hardware and/or a combination of software and hardware. Variousembodiments are directed to apparatus, e.g., mobile nodes such as mobileterminals, base stations, communications system. It is also directed tomethods, e.g., method of controlling and/or operating mobile nodes, basestations and/or communications systems, e.g., hosts. Various embodimentsare also directed to machine readable medium, e.g., ROM, RAM, CDs, harddiscs, etc., which include machine readable instructions for controllinga machine to implement one or more steps.

In various embodiments nodes described herein are implemented using oneor more modules to perform the steps corresponding to one or moremethods, for example, signal processing, message generation and/ortransmission steps. Thus, in some embodiments various features areimplemented using modules. Such modules may be implemented usingsoftware, hardware or a combination of software and hardware. Many ofthe above described methods or method steps can be implemented usingmachine executable instructions, such as software, included in a machinereadable medium such as a memory device, e.g., RAM, floppy disk, etc. tocontrol a machine, e.g., general purpose computer with or withoutadditional hardware, to implement all or portions of the above describedmethods, e.g., in one or more nodes. Accordingly, among other things,various embodiments are directed to a machine-readable medium includingmachine executable instructions for causing a machine, e.g., processorand associated hardware, to perform one or more of the steps of theabove-described method(s).

While described in the context of an OFDM system, at least some of themethods and apparatus of various embodiments are applicable to a widerange of communications systems including many non-OFDM and/ornon-cellular systems.

Numerous additional variations on the methods and apparatus of thevarious embodiments described above will be apparent to those skilled inthe art in view of the above description. Such variations are to beconsidered within the scope. The methods and apparatus of theembodiments may be, and in various embodiments are, used with CDMA,orthogonal frequency division multiplexing (OFDM), and/or various othertypes of communications techniques which may be used to provide wirelesscommunications links between access nodes and mobile nodes. In someembodiments the access nodes are implemented as base stations whichestablish communications links with mobile nodes using OFDM and/or CDMA.In various embodiments the mobile nodes are implemented as notebookcomputers, personal data assistants (PDAs), or other portable devicesincluding receiver/transmitter circuits and logic and/or routines, forimplementing the methods.

What is claimed is:
 1. A method of operating a base station for uplinktraffic scheduling, the method comprising: receiving a transmissionbacklog report from a wireless terminal, said transmission backlogreport communicating a report value; and determining a reporting controlfactor corresponding to said received report, said reporting controlfactor being a function of at least one of channel quality information,wireless terminal available transmission power information, wirelessterminal device capability information or quality of serviceinformation.
 2. The method of claim 1, wherein said report value is amulti-bit report value.
 3. The method of claim 1, further comprising:interpreting said received report value as a function of said determinedreporting control factor.
 4. The method of claim 3, wherein interpretingsaid received report value as a function of said determined reportingcontrol factor includes determining backlog information relating toframes to be transmitted by said wireless terminal.
 5. The method ofclaim 4, wherein said reporting control factor is a function of channelquality information; and wherein said channel quality informationincludes at least one of uplink interference information, downlinkinterference information, uplink signal to noise information, downlinksignal to noise information, uplink signal to interference information,and downlink signal to interference information.
 6. The method of claim5, wherein said channel quality information includes uplink interferenceinformation, and wherein said uplink interference information includesbeacon ratio report information, the method further comprising: prior tosaid step of determining the reporting control factor, receiving abeacon ratio report from said wireless terminal.
 7. The method of claim4, wherein said reporting control factor is a function of wirelessterminal transmission power information, the method further comprising:prior to said step of determining the reporting control factor,receiving a transmission power information report from said wirelessterminal.
 8. The method of claim 4, wherein said step of determining areporting control factor includes estimating the maximum number offrames of information that the wireless terminal will be able tocommunicate in a segment if said segment is allocated to the wirelessterminal.
 9. The method of claim 5, wherein said reporting controlfactor is a function of another factor, the method further comprising:prior to receiving said transmission backlog report broadcast a valuerepresenting said another factor.
 10. The method of claim 4, furthercomprising: receiving a second transmission backlog report from saidwireless terminal, said second transmission backlog report communicatinga second report value said second transmission backlog report being ofthe same type as the transmission backlog report; determining areporting control factor corresponding to said second received report,said reporting control factor corresponding to said second receivedreport being a function of at least one of channel quality information,wireless terminal available transmission power information, wirelessterminal device capability information or quality of serviceinformation; and interpreting said received second report value as afunction of said determined second reporting control factor.
 11. Themethod of claim 10, wherein said report value and said second reportvalue are the same, wherein said corresponding control factor values aredifferent, and wherein interpreting said received second report valuedetermines different backlog information relating to frames to betransmitted by said wireless terminal than interpreting said receivedreport value.
 12. The method of claim 4, wherein determining a reportingcontrol factor includes determining a reporting control factor type fromamong a plurality of reporting control factor types as a function of abit pattern of at least a portion of the received report value.
 13. Themethod of claim 4, further comprising: receiving an additionaltransmission backlog report from a wireless terminal, said additionaltransmission backlog report communicating another report value; anddetermining to interpret said received another report value withoutusing a reporting control factor, said decision to interpret withoutusing a reporting control factor being performed as a function of a bitpattern of at least a portion of said received another report value. 14.A base station for uplink traffic scheduling comprising: a receivermodule for receiving reports from wireless terminals said reportsincluding transmission backlog reports wherein a transmission backlogreport communicates a report value; and a reporting control factordetermination module for determining a value of a reporting controlfactor, said reporting control factor being a function of at least oneof channel quality information, wireless terminal available transmissionpower information, wireless terminal device capability information orquality of service information.
 15. The base station of claim 14,wherein said report value is a multi-bit report value.
 16. The basestation of claim 14, further comprising: an report interpretation modulefor interpreting said received report value as a function of adetermined reporting control factor.
 17. The base station of claim 16,wherein said report interpretation module determines backlog informationrelating to frames to be communicated by a wireless terminal whichtransmitted the received backlog report.
 18. The base station of claim17, wherein said reporting control factor determination moduledetermines said reporting control factor as a function of channelquality information; and wherein said channel quality informationincludes at least one of uplink interference information, downlinkinterference information, uplink signal to noise information, downlinksignal to noise information, uplink signal to interference information,and downlink signal to interference information.
 19. The base station ofclaim 18, wherein said channel quality information includes uplinkinterference information, wherein said uplink interference informationincludes beacon ratio report information, and wherein said receiver alsoreceives beacon ratio reports, the base station further comprising: abeacon ratio report module for recovering a beacon ratio report valuecommunicated from a wireless terminal.
 20. The base station of claim 17,wherein said reporting control factor is a function of wireless terminaltransmission power information and wherein said receiver also receiveswireless terminal transmission power reports, the base station furthercomprising: a wireless terminal transmission power report recoverymodule for determining wireless terminal transmission power availabilityinformation.
 21. The base station of claim 17, wherein at least somereporting control factors are determined as a function of a currentmaximum wireless terminal rate option, the base station furthercomprising: a wireless terminal maximum rate determination module fordetermining the maximum rate option that said wireless terminal is touse for an uplink traffic channel segment.
 22. The base station of claim17, wherein at least some reporting control factors are determined as afunction of an adjustment parameter which is broadcast over a broadcastcommunications channel, the base station further comprising: atransmitter for transmitting said adjustment parameter.
 23. A basestation for uplink traffic scheduling comprising: means for receivingreports from wireless terminals said reports including transmissionbacklog reports wherein a transmission backlog report communicates areport value; and determination means for determining a value of areporting control factor, said reporting control factor being a functionof at least one of channel quality information, wireless terminalavailable transmission power information, wireless terminal devicecapability information or quality of service information.
 24. The basestation of claim 23, wherein said report value is a multi-bit reportvalue.
 25. The base station of claim 23, further comprising: means forinterpreting said received report value as a function of a determinedreporting control factor.
 26. The base station of claim 25, wherein saidmeans for interpreting said received report value determines backloginformation relating to frames to be communicated by a wireless terminalwhich transmitted the received backlog report.
 27. The base station ofclaim 26, wherein said determination means determines said reportingcontrol factor as a function of channel quality information; and whereinsaid channel quality information includes at least one of uplinkinterference information, downlink interference information, uplinksignal to noise information, downlink signal to noise information,uplink signal to interference information, and downlink signal tointerference information.
 28. The base station of claim 27, wherein saidchannel quality information includes uplink interference information,wherein said uplink interference information includes beacon ratioreport information, and wherein said receiver also receives beacon ratioreports, the base station further comprising: a beacon ratio reportmeans for recovering a beacon ratio report value communicated from awireless terminal.
 29. The base station of claim 26, wherein saidreporting control factor is a function of wireless terminal transmissionpower information and wherein said receiver also receives wirelessterminal transmission power reports, the base station furthercomprising: transmission power information recovery means fordetermining wireless terminal transmission power availabilityinformation from a received wireless terminal transmission power report.30. The base station of claim 26, wherein at least some reportingcontrol factors are determined as a function of a current maximumwireless terminal rate option, the wireless terminal further comprising:wireless terminal transmission rate determination means for determiningthe maximum rate option that said wireless terminal is to use for anuplink traffic channel segment.
 31. The base station of claim 26,wherein at least some reporting control factors are determined as afunction of an adjustment parameter which is broadcast over a broadcastcommunications channel, the base station further comprising: means fortransmitting for transmitting said adjustment parameter.
 32. Anon-transitory computer readable medium embodying machine executableinstructions for controlling a base station to implement a method foruplink traffic scheduling, the method comprising: receiving atransmission backlog report from a wireless terminal, said transmissionbacklog report communicating a report value; and determining a reportingcontrol factor corresponding to said received report, said reportingcontrol factor being a function of at least one of channel qualityinformation, wireless terminal available transmission power information,wireless terminal device capability information or quality of serviceinformation.
 33. The non-transitory computer readable medium of claim32, wherein said report value is a multi-bit report value.
 34. Thenon-transitory computer readable medium of claim 32, further embodyingmachine executable instructions for: interpreting said received reportvalue as a function of said determined reporting control factor.
 35. Thenon-transitory computer readable medium of claim 34 further embodyingmachine executable instructions for: determining backlog informationrelating to frames to be transmitted by said wireless terminal as partof said step of interpreting said received report value as a function ofsaid determined reporting control factor includes.
 36. Thenon-transitory computer readable medium of claim 35, wherein saidreporting control factor is a function of channel quality information;and wherein said channel quality information includes at least one ofuplink interference information, downlink interference information,uplink signal to noise information, downlink signal to noiseinformation, uplink signal to interference information, and downlinksignal to interference information.
 37. The non-transitory computerreadable medium of claim 36, wherein said channel quality informationincludes uplink interference information, and wherein said uplinkinterference information includes beacon ratio report information, themethod further comprising: prior to said step of determining thereporting control factor, receiving a beacon ratio report from saidwireless terminal.
 38. The non-transitory computer readable medium ofclaim 35, wherein said reporting control factor is a function ofwireless terminal transmission power information, the computer readablemedium further embodying machine executable instructions for: receivinga transmission power information report from said wireless prior to saidstep of determining the reporting control factor.
 39. An apparatusoperable in a communication system for uplink traffic scheduling, theapparatus comprising: a processor configured to: receive a transmissionbacklog report from a wireless terminal, said transmission backlogreport communicating a report value; and determine a reporting controlfactor corresponding to said received report, said reporting controlfactor being a function of at least one of channel quality information,wireless terminal available transmission power information, wirelessterminal device capability information or quality of serviceinformation.
 40. The apparatus of claim 39, wherein said report value isa multi-bit report value.
 41. The apparatus of claim 39, wherein theprocessor is configured to: interpret said received report value as afunction of said determined reporting control factor.